[Bug]: data360 search rejects its own declared limit parameter with JSON_PARSER_ERROR

### Summary

On the Data 360 MCP server, `search` rejects the `limit` parameter that its own published `inputSchema` declares.

### Environment

Production org (Enterprise Edition), API v67. Client: Claude Code via a pre-registered External Client App (public client, PKCE, `mcp_api` scope). Server `data.data360`, URL `https://api.salesforce.com/platform/mcp/v1/data/data360`, activated and probed 2026-09-02.

### Detail

`limit` appears in the `inputSchema` returned by `tools/list` for `search`. Passing it:

```
JSON_PARSER_ERROR: Unrecognized field "limit"
```

Omitting it lets the call succeed. So the schema the server publishes and the payload the server accepts disagree.

### Why this matters

Clients build calls from the advertised schema, and a well-behaved client that honours the schema fails on a parameter the server told it about. Result-set control also matters here specifically: `search` is the discovery entry point to a catalogue of several hundred operations, and it is the natural place to want a bounded result set.

### Suggested resolution

Accept `limit`, or remove it from the published `inputSchema` so the two agree.

Start by comparing the search entry in the tools/list inputSchema with the payload validation that produces JSON_PARSER_ERROR. Verify the behavior against the documented production request: done means limit is accepted, or it is removed from the published schema so advertised and accepted parameters agree.

Written by the indexing model from the issue text.