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

Annotations already mark destructiveHint=true and readOnlyHint=false. The description adds 'Irreversible' and 'Requires allow_writes', which are more specific than the hints. However, it does not disclose other side effects (e.g., impact on related documents) or what happens on success/failure. With annotations providing the safety profile, the added value is moderate.

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 sentences, front-loaded with 'ATO FISCAL REAL', and every word adds value. No fluff or repetition.

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 destructive fiscal operation with no output schema, the description gives critical warnings (irreversibility, require allow_writes) but misses important context: return values, prerequisites (e.g., authorized CT-e), and parameter meanings beyond ids. It is adequate but not comprehensive.

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 0%, so the description must compensate. It only implicitly covers 'ids' (CT-e IDs) but leaves 'account' and 'empresa_id' completely unexplained. Given all three parameters are required contextually, the lack of clarification for two parameters is a significant gap.

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: cancels one or more CT-e by ID with SEFAZ, and distinguishes it from other CT-e operations like averaging or emission. The verb 'cancels' and resource 'CT-e' are specific, and the phrase 'ATO FISCAL REAL' emphasizes its fiscal nature.

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 mentions 'Irreversible' and 'Requires allow_writes', which imply caution and permission prerequisites. However, it does not explicitly state when to use this versus alternative tools like hivecloud_cte_excluir, or what conditions must be met (e.g., CT-e must be authorized). The guidance is clear but could be more explicit.

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