search

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint. Description adds crucial behavioral detail: does not fetch document bodies during search to respect rate limits, and guides to use fetch separately. No contradiction.

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?

Two sentences front-loaded with purpose and audience, followed by behavioral constraint and guidance. No wasted words, every sentence adds value.

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?

Given simple tool (1 param, output schema exists), description covers purpose, audience, sibling guidance, and output format. Could add minor details like query format expectations, but overall 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 100% with parameter 'query' described as 'Turkish search query'. Description adds no additional meaning beyond 'Turkish' from schema, so baseline 3 is appropriate.

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?

The description clearly states 'Searches Bedesten-supported Turkish court databases' with specific verb and resource, and distinguishes from sibling 'search_bedesten_unified' by specifying this is for ChatGPT Deep Research only.

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 states 'Only for ChatGPT Deep Research' and recommends 'For regular MCP use, prefer search_bedesten_unified', providing clear when-to-use and alternatives. Also advises calling fetch for bodies to stay within rate limits.

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