Edit Template

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

Annotations already indicate write/destructive behavior, and the description adds valuable context: 'Only provided fields change' explains merge semantics, and 'BLOCKED in read-only mode' warns about operating mode. This goes beyond the structured hints without contradicting them.

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 two short sentences, front-loaded with the core action, with no wasted words. It efficiently conveys the action, partial-update semantics, and the read-only restriction.

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 an output schema present, return details are not needed. The description covers the essential behavior (update existing, partial fields, read-only block) and the field list is available in the schema. It is sufficiently complete for a simple edit tool, though it could mention prerequisites or errors.

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 14% (only template_id_or_alias has a description). The description's general statement about partial updates is helpful but does not explain individual parameters like layout_template or html_body. Given the low coverage, the description should compensate more but does not.

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 ('Update an existing template') with a specific verb and resource, distinguishing it from sibling tools like create_template and delete_template. The additional phrase 'Only provided fields change' clarifies the partial-update semantics, reinforcing the purpose.

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 clear context for when to use this tool—when modifying an existing template—and mentions the behavioral rule 'Only provided fields change.' It does not explicitly name alternatives like create_template, but the context is sufficient given the sibling list.

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