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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe-read behavior is known. The description adds the bulk execution trait and clarifies the single-item scope via 'específico pelo id,' which is useful context. However, it does not disclose batch limits, response format, or error modes, making the added transparency moderate but not rich.

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, with the purpose front-loaded and the bulk support note immediately after. Every sentence provides distinct information, and there is no redundant or filler content. It is appropriately concise for a simple retrieval tool.

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?

Given the read-only, idempotent nature and no output schema, the description is minimally viable but omits important context. It does not explain what 'detalha' includes, how batches are returned, or what the 'account' and 'empresa_id' parameters are for. The bulk feature and 5-parameter complexity warrant more detail than this short description provides.

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 schema has 0% description coverage, so the description must compensate. It mentions 'id', 'ids', and 'empresa_ids' but omits 'account' and 'empresa_id' entirely, and does not clarify parameter relationships or precedence (e.g., whether id and ids are mutually exclusive). For a 5-parameter tool with no other documentation, this partial explanation is insufficient.

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: 'Detalha um CT-e específico pelo id' (details a specific CT-e by id), providing a specific verb, resource, and scope. It distinguishes from list tools (hivecloud_list_ctes) and mutating tools (hivecloud_cte_emitir, cancelar) by indicating a read/detail operation. However, it does not explicitly differentiate from hivecloud_cte_xml, which also retrieves a CT-e, and no alternative tools are named.

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?

The only usage guidance is the bulk support line: 'accepts ids, empresa_ids for batched execution.' This indicates when to use the array parameters, but there is no explicit statement about when to use this tool versus alternativas like hivecloud_list_ctes or hivecloud_cte_xml, nor any exclusions or preconditions. The context is implied rather than explicit.

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