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

The description adds important context by calling delete 'irreversível', but this directly contradicts the annotation destructiveHint=false. An irreversible delete is destructive, so the description and annotation are in conflict.

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 delete line is short and clear, but the description dedicates significant space to create/update field lists that are irrelevant for a delete-only flattened tool. This clutter reduces conciseness without adding value for the actual operation.

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 delete tool with no output schema and misleading annotations, the description should cover success/failure behavior, account handling, and whether template_token is the only needed parameter. It only mentions irreversibility, leaving key operational details unexplained.

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?

With 0% schema description coverage, the description must compensate. It only clarifies that template_token identifies the template for deletion, but does not explain account or data parameters, nor does it state requiredness or parameter format.

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 explicitly states 'delete (template_token): irreversível' and ends with '[Flattened action: delete]', making it clear the core operation is deleting a template. However, it also lists create/update actions, which introduces ambiguity about whether this exact tool can perform those operations.

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?

No guidance is given on when to use this delete tool versus the create/update siblings. The description merely enumerates all possible actions without stating 'use delete only to permanently remove a template' or explicitly excluding create/update from this flattened tool.

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