list_templates

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

With no annotations provided, the description carries full burden. It discloses that the output is automatically stored with an object ID and can be referenced in other functions, which is valuable behavioral context beyond the schema. However, it does not specify whether the operation is read-only or mention auth needs 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 moderately concise with the main purpose in the first sentence. The parameter documentation and object store behavior are useful but could be streamlined slightly. It is well-structured and front-loaded.

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 simplicity of the tool (list, two optional params, no output schema), the description covers parameters and the object store behavior. However, it lacks information on pagination, error handling, or guidance on when to use this tool versus similar sibling tools like 'list_pipelines' or 'search_templates'.

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 description coverage is 0%, so the description must compensate. It explains both parameters: 'limit' (maximum number, default 100) and 'pipeline_type' (type of pipeline). This adds meaning beyond the schema's type and default fields. However, it could specify that pipeline_type accepts 'query' or 'indexing' as per the enum definition.

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 that the tool retrieves a list of all available pipeline and indexing templates. The verb 'retrieves' and specific resource 'list of templates' make the purpose unambiguous. It distinguishes from siblings like 'get_template' (single) and 'search_templates' (search).

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 that this tool is for listing templates but does not explicitly state when to use it versus alternatives like 'search_templates' or 'get_template'. It lacks guidance on prerequisites or context, though the purpose is clear.

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