proxy_search_tools

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses that it is a lazy loading search that returns a ranked list (name, desc, score, tags). No annotations provided, but description does not mention side effects or safety; assumes read-only. Could be more explicit about no destructive behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise at 4 sentences. Front-loaded with purpose and usage. The last sentence about inspiration is slightly extraneous but not harmful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Explains purpose, usage, and output. Lacks details on query syntax, limit effect, and error handling. Since output schema exists, return values are covered, but tool behavior could be more complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% (no parameter descriptions in schema). Description only refers to 'free-text query' for the query parameter and mentions output format but not limit. Insufficient to clarify parameter usage beyond basic intent.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it searches the catalogue for servers/tools using free-text query. Distinguishes from siblings by emphasizing lazy loading pattern for on-demand discovery, avoiding context bloat.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains when to use (on-demand discovery to find specific capabilities) and what to do after (use proxy_activate_server or handshake). No explicit exclusions but enough context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.