search_templates

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

Annotations readOnlyHint=true and idempotentHint=true already indicate safety. Description adds behavioral clarity about mode behavior, but doesn't mention pagination or rate limits. No contradiction with annotations.

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?

The description is a single long sentence that front-loads the core purpose. It could be more structured (e.g., bullet points) but remains concise given the complexity. 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?

While schema covers parameters, the description does not describe the response format or pagination behavior. With no output schema, the description should hint at what the response contains. This is a gap, but the tool is read-only and search-oriented, so moderate completeness.

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 descriptions. The description enhances understanding by linking parameters to specific search modes (e.g., 'For searchMode=by_nodes: array of node types'). This adds value beyond schema.

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 the tool searches templates and lists five distinct search modes. It distinguishes from sibling tools like search_nodes and get_template by focusing on templates and detailing mode-specific purposes.

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?

The description explicitly tells when to use each search mode (e.g., 'Use searchMode='keyword' for text search'). It implicitly differentiates from siblings by focusing on templates. Missing explicit 'when not to use' but sufficient for typical use.

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