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 pagination via 'after' parameter and 'next_cursor' response, and explains that output is automatically stored and can be referenced via object ID. However, it does not mention rate limits or authorization needs, which are less critical for a read-only list endpoint.

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 well-structured with parameter documentation and return behavior. It is concise, with each sentence adding value, though the object storage guidance could be integrated more tightly.

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, the description covers return format (list, object ID, store), cursor pagination, and a note about error messages. It adequately handles three parameters, but could mention empty result cases.

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 each parameter: limit (default 100), pipeline_type (type of pipeline), and after (cursor for pagination). It adds operational meaning beyond the schema's type definitions.

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 retrieves a list of all available pipeline and indexing templates. It uses a specific verb ('retrieves') and resource ('templates'), distinguishing it from sibling tools like list_indexes and list_pipelines.

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 does not provide guidance on when to use this tool versus alternatives such as search_templates. It mentions pagination but lacks explicit context for when this tool is appropriate or when to use other tools.

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