list_templates

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

With no annotations, the description carries the full burden, and it does disclose the returned fields (id, name, bind_model, slot_count) and the account-level scope, which is useful since there is no output schema. It says nothing about pagination, result ordering, or volume limits, which matters for an unbounded list tool.

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?

A single front-loaded sentence with the resource first and the projected fields in parentheses — no wasted prose. The parenthetical field list is slightly redundant with an output schema, but none exists here, so it earns its place.

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?

For a parameterless list tool with no annotations and no output schema, naming the account scope and the returned fields covers what an agent needs to select and call it. Missing only secondary detail such as ordering or whether the result set is bounded.

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 tool takes zero parameters, so the baseline is 4. The description correctly implies no filtering is possible and that all templates for the account are returned.

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?

States a specific verb+resource ('List the account's templates') and enumerates the fields returned, so an agent can distinguish it from get_template (single) and create/update/delete_template. It does not explicitly name a sibling to route away from, keeping it at 4 rather than 5.

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?

Usage is only implied by the verb 'List' — the description never says when to use this versus get_template for a known id or list_starters as an alternative catalog. For a zero-argument enumeration tool the intent is fairly self-evident, but no explicit guidance or exclusions are given.

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