search_templates

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

Without annotations, the description carries the burden and does disclose that the output is automatically stored and can be referenced via object IDs, and recommends using object store tools. However, it omits details on side effects, authorization, or rate limits.

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 structured with a brief purpose line followed by parameter and return documentation, but includes extra text about object storage that could be integrated more concisely. It is not overly verbose but not maximally efficient.

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 no output schema and low schema coverage, the description covers the search mechanism, parameters, returned preview, and follow-up actions using object store. Missing error conditions or limitations, but adequate 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?

Schema coverage is 0%, but the description adds meaning to all three parameters: query is the search query, top_k controls the maximum results (with default 10), and pipeline_type specifies the type ('indexing' or 'query', default 'query'). This clarifies beyond the schema's types and defaults.

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 for pipeline or indexing templates using semantic similarity, with a specific verb and resource. It distinguishes from sibling tools like list_templates (which lists all) and get_template (which retrieves a specific template).

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 via semantic search, but does not explicitly provide when to use versus alternatives like list_templates or search_docs. No exclusions or conditional guidance is given.

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