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

Annotations already cover the read-only/destructive/idempotence profile, and the description adds behavioral context beyond them: the draft-only constraint, required scope `templates:manage`, and a definitive endpoint mapping. It does not describe the outcome of attempting to modify a published template, but this is a minor gap.

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?

Five short lines, front-loaded with the purpose and key constraint. The endpoint, scope, and rate-limit lines are useful guardrails, and there is no 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?

This is a 16-parameter tool with a deeply nested `structure` object and no output schema, yet the description does not state what the call returns, how errors for published templates are surfaced, or which top-level fields are updatable. The draft-only constraint and scope are helpful, but they do not make the definition complete for such a complex operation.

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 only 31%, so the description needed to compensate, but it only mentions the id via the PATCH path. It gives no guidance on `structure`, `pass_style`, `wallet_types`, image IDs, or partial-update semantics beyond the PATCH verb.

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 clear action ('Update a template') and immediately narrows it with 'Updates a draft template. Published templates cannot be modified.' This distinguishes it from createTemplate, publishTemplate, and deleteTemplate, giving the agent a concrete resource and scope.

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 tells the agent this tool is for draft templates and that published templates are off-limits, which is a clear when-not condition. It does not explicitly name alternatives such as publishTemplate for published templates, 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.