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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds real value beyond that: the scope of templates returned, the field shape, the null-vs-organisation semantics of the owning org, and the downstream cloning behavior in traceable_doc_create.

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, purpose front-loaded, with the field enumeration and the workflow hint following. The field list is dense but each item is informative; nothing is redundant, though the long comma-delimited enumeration is slightly heavy for a single clause.

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?

With no output schema, the description carries the burden of describing the return shape, and it does so by listing the fields and the null semantics for system templates. It is complete enough to call correctly; only minor things like ordering or result size are unspecified.

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 per the rubric the baseline is 4. The description's mention of templateId is about a different tool's input, not this one's, so there is nothing further to document here.

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?

Specific verb ("List") plus a precisely scoped resource ("the document templates available to you (system templates plus your organisations')"), and it enumerates the exact fields returned. No sibling tool lists templates, so there is nothing to confuse it with; an agent knows immediately what this does.

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 gives clear downstream context: use a template's id as templateId in traceable_doc_create to clone its bands and body scaffold, which tells the agent why and when to call this. It stops short of stating any exclusions or alternative sources of the same data, so it is strong context without explicit when-not guidance.

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