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

Annotations already mark the tool read-only, idempotent, and non-destructive, so the description need not repeat that. It adds genuinely useful behavior beyond the annotations: the preset is 'immutable' and 'validated,' and the rendered HTML/CSS is intentionally empty in v1, which prevents an agent from expecting populated markup. No contradiction with annotations.

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, with the primary action front-loaded and the v1 caveat in a short second sentence. There is no filler or redundant restatement of the tool name. The dense phrase 'selected immutable, validated semantic preset' is the only minor clarity cost, but overall the description is efficient.

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 annotations, fully documented parameters, and existing output schema, the description covers the important non-obvious facts: single-workspace ownership, immutable/validated preset, and empty rendered HTML in v1. It would be slightly better if it pointed to list_invoice_templates as the enumeration sibling, but nothing needed to call the tool 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?

Schema description coverage is 100%, so the schema already documents templateId and version. The description adds little parameter-level meaning beyond the 'workspace-owned' scope and the existence of the preset; the schema already explains the version default and the company-owned template ID.

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 a specific verb ('Retrieve'), identifies the resource ('one workspace-owned invoice template'), and names the companion payload ('selected immutable, validated semantic preset'). The singular 'one' distinguishes it from list_invoice_templates, the template focus separates it from get_invoice, and the v1 HTML/CSS caveat clarifies what this tool returns versus a rendered-template tool.

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 use when a single template plus its preset is needed, and the 'workspace-owned' and 'intentionally empty' phrasing adds context. However, it never explicitly names alternatives such as list_invoice_templates or get_invoice, nor does it state when not to use this tool.

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