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

With no annotations, the description carries the full burden, and it does disclose that template_id triggers replacement and that the affected template is owner- or office-scoped. It still omits important mutation details such as overwrite behavior, permissions, and whether omitted fields are preserved.

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 clauses with no filler, and the core purpose is front-loaded before the update/replacement detail. Every part contributes useful information.

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 mutation tool with no annotations, no output schema, and low schema description coverage, the description is only partially complete. It covers the main purpose and replacement behavior but does not describe return values, permission requirements, or enough field-level semantics to be fully self-contained.

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 low at 20%, so the description needs to compensate. It explains the purpose of lines, options, and template_id, but does not clarify shop_id or name, leaving required-parameter semantics partly inferred from the schema.

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 states a specific verb and resource: save a quote template, including worker-written lines and good/better/best options. It is clearly distinct from templates_list and templates_archive by action, though it does not explicitly name those siblings as alternatives.

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 implies the use case of creating a reusable template to start quotes from, and explains that supplying template_id replaces an existing template. However, it gives no explicit when-to-use guidance versus alternatives such as quotes_create or templates_archive.

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