search_templates

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is clear. The description adds behavioral context beyond annotations, notably explaining that 'patterns' mode returns lightweight workflow pattern summaries mined from 2700+ templates. It does not contradict 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, well-structured sentence that front-loads the main purpose and then enumerates modes concisely. Every sentence earns its place with no redundancy or filler.

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 13 parameters with no required ones and no output schema, the description covers all modes and parameter associations. It explains the intent of each search mode and how parameters interact, making it complete for the tool's complexity.

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?

With 100% schema description coverage, baseline is 3. The description adds value by linking each parameter to its applicable searchMode context (e.g., 'For searchMode=by_task: the type of task'), clarifying usage beyond the schema's per-parameter descriptions. This aids correct selection.

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 with multiple modes, listing each mode's purpose (keyword, by_nodes, by_task, by_metadata, patterns). It effectively distinguishes from sibling tools like search_nodes (node search) and get_template (single template retrieval) by emphasizing multi-modal search capability.

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 provides explicit conditions for each searchMode parameter, guiding when to use which mode (e.g., 'searchMode=keyword for text search'). While it lacks explicit when-not-to-use or alternative tool references, the mode-specific guidance is clear and actionable.

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