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

Annotations already declare readOnly/idempotent/non-destructive behavior, and the description adds matching context by saying 'não altera o documento' and noting the returned URL is temporary. It also clarifies that one or more CT-e can be processed in a single call, which is useful beyond the schema.

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?

Two concise sentences lead with the main action, then add scope, output, and side-effect information. No filler or redundant restatement of the tool name.

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?

The description covers purpose, applicable state ('autorizados'), output, and side-effect safety, which is enough for a low-complexity read-only tool without an output schema. The main gap is incomplete parameter semantics for account/empresa_id, but the core invocation path is clear.

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 schema description coverage at 0%, the description must compensate for undocumented parameters. It only clarifies that 'ids' refers to one or more authorized CT-e; 'account' and 'empresa_id' receive no explanation, leaving meaningful ambiguity for a 3-parameter tool.

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 ('Gera o PDF do DACTE') and clearly identifies the resource ('um ou mais CT-e autorizados') and the output (temporary download URL). This distinguishes it from sibling tools like hivecloud_cte_xml or hivecloud_cte_emitir.

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 states the target condition ('CT-e autorizados') and compares the behavior to the issuer's 'Imprimir DACTe' button, giving users a clear mental model of when to invoke it. It does not explicitly name alternative tools or list exclusion cases, so it falls short of a 5.

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