search_templates

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Search', which suggests a read-only operation, but it does not disclose return format, case sensitivity, pagination, or any potential side effects. This lack of behavioral detail is a significant gap.

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 concise sentence that front-loads the action and resource. It uses no unnecessary words and is easy to parse, making it appropriately sized for this simple search tool.

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 the tool is a simple search with two parameters and no output schema or annotations, the description provides the minimum viable information. However, it lacks context about result format, search behavior nuances, or integration with sibling tools, leaving it somewhat incomplete for an agent to fully understand what to expect.

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?

The schema already provides descriptions for both parameters (query and category), achieving 100% coverage. The description adds value by clarifying that the query searches across name, description, or tags, which goes beyond the schema's generic 'Search query string'. However, the category parameter remains only 'Optional category filter' with no further elaboration.

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's action ('Search') and target ('templates'), and specifies that search can be performed by name, description, or tags. This distinguishes it from the sibling tool 'list_templates', which likely returns all templates without a search query.

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 implies usage when searching for templates by name, description, or tags, but it does not explicitly state when to use this tool versus alternatives like list_templates. There are no 'when not to use' statements or reference to other tools, so guidance is only implied.

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