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

The description adds meaningful behavioral detail beyond the annotations: the Draft itself is unchanged, the call requires an Authorization: Bearer zs_... header, and it returns template_id and role names. It does not contradict the annotations, which only state readOnly false, idemptotent false, destructive false.

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?

Every sentence contributes a distinct piece of information: purpose, API equivalence, no blank-template flow, return value, side-effect on the Draft, and authentication. The main action is front-loaded and no sentence is wasted.

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 two-parameter tool with an output schema, the description covers purpose, prerequisites, side effects, return values, and auth requirements. The principal gap is that the parameters are not formally described in the description, especially 'name', though document_id is inferable from the endpoint context.

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 input schema has 0% description coverage, so the description must compensate for parameter meaning. The endpoint mirrors /drafts/{id}and the phrase 'existing Draft' imply document_id is the draft ID, but the description never explicitly maps document_id or name to their meanings. In particular, 'name' remains unexplained.

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 and resource: 'Save an existing Draft as a reusable template.' It also explicitly rules out a blank-template flow, which distinguishes it from broader template-creation ideas and from siblings like list_templates or send_from_template.

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?

It clearly states the prerequisite: start from an existing Draft, and that there is no blank-template flow. It does not explicitly name alternative tools for sending or listing templates, but the usage context is clear enough for an agent to decide when to invoke it.

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