list_document_templates

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

The description adds no behavioral context beyond what the annotations already declare. Annotations thoroughly cover safety (readOnlyHint, idempotentHint, destructiveHint false), but the description fails to add value such as noting there are no filters, no pagination, or that it returns all templates. It merely restates the title.

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 extremely concise at three words, with no filler. It is front-loaded and every word is meaningful. While terse, it is appropriately sized for a tool with no parameters and a straightforward purpose.

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 tool's extreme simplicity (no parameters, no output schema, simple list operation), the description is nearly complete. It clearly states what the tool does. However, it omits any detail about return values or scope, though for a no-param list with openWorldHint, this is largely implicit.

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?

There are zero parameters, so the schema fully covers everything needed. The baseline for 0 params is 4, and the description does not need to compensate for missing parameter explanations. It correctly focuses on the action rather than params.

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 action ('List') and the resource ('document templates'), making the tool's purpose evident. However, it does not explicitly differentiate this from other list_* tools with similar naming patterns, such as list_document_settings or list_company_profiles, so it stops short of full sibling discrimination.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of typical use cases, prerequisites, or exclusions. The openWorldHint annotation implies it lists all templates, but this is not stated in the description itself.

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