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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), and the description goes beyond them by enumerating the returned fields — id, name, TraceID prefix, document type, band previews, body outline, organisation details. It also discloses that organisationId/organisationName are null for system templates, which is a real behavioral nuance. It stops short of describing ordering or volume behavior.

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?

Two sentences, front-loaded with the action and then the field enumeration. The long list of returned fields is dense but justified given there is no output schema. No filler sentences.

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 zero-param, read-only list tool with no output schema, the description carries the return-value burden itself and does so completely, while annotations cover safety and the workflow to traceable_doc_create is spelled out. Nothing needed to call it correctly is missing.

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?

Zero parameters, so there are no argument semantics to clarify; the schema is empty and the baseline is 4. The description appropriately spends its budget on the return shape instead.

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 and resource ('List the document templates') plus the exact scope (system templates plus the caller's organisations'). It also routes the agent to the downstream sibling traceable_doc_create, so the tool is distinguishable from its neighbors without opening a schema.

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?

Explicitly tells the agent what to do with the results ('Pass a template's id as templateId to traceable_doc_create to clone...'), giving a clear purpose context. It does not state when-not to use it, but there is no overlapping sibling that lists templates, so the missing exclusion is minor.

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