search_tools

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

No annotations provided, but the description adds value by explaining it's a meta tool and implements MCP Tool Search Tool semantics. Discloses its purpose and function adequately for a search tool with no side effects implied.

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?

Three sentences, front-loaded with 'Meta tool,' concise and to the point. Every sentence adds value with no wasted words.

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?

For a simple meta-tool with one parameter and an output schema, the description is complete. It explains what it does, why it's useful, and how it differs from sibling tools.

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 100% with parameter description 'What the user wants to do, in plain language.' The description's mention of 'plain-English intent' reinforces the schema but does not add new details beyond it.

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?

Description clearly states it's a meta tool that takes plain-English intent and returns ranked tool suggestions. Distinguishes itself from sibling tools by being a meta-tool that selects among them.

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?

Explicitly says it saves the agent from listing every tool description when one tool fits the ask, providing clear usage context. Does not explicitly state when not to use or alternatives, but the context is sufficient.

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