decisio_list_templates

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

The word 'List' signals a read-only operation, and the mention of returning criteria/options gives some behavioral insight. However, with no annotations, the description does not explicitly state that it makes no changes, nor does it disclose any rate limits or other runtime behavior. More explicit transparency would be beneficial.

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, well-structured sentence that leads with the action word and packs in the key information: what is listed and what those items contain. There is no redundancy or filler.

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 simple, parameterless list tool, the description adequately covers the necessary information: it states the output (templates) and the content included (default criteria and options). It does not discuss formatting or ordering, but these are unlikely to be essential for such a straightforward tool.

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 accepts no parameters, so the description is not required to explain parameter semantics. The baseline for 0-parameter tools is 4, and the description adds no confusion about inputs.

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 uses the direct verb 'List' and clearly identifies the resource as 'available decision templates' with their default criteria and options. This differentiates it from siblings that create, compare, calculate, or advise, making its function unmistakable.

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 context: when you need to see available templates before creating a decision. It is clear but does not explicitly mention alternative tools or exclusion scenarios, so it stops short of a 5.

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