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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces 'Não altera o documento'. It adds useful behavioral context beyond annotations: the download URL is temporary, and the connection requires mdfe_tenant_id. No contradiction with annotations.

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 the main action and result, followed by two important caveats. Every word earns its place; no fluff or verbosity.

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 explains the main return value (temporary URL) and safety characteristics, which is adequate for a simple read tool. However, it omits details about optional parameters (account, empresa_id) and does not specify the URL's lifetime or zip structure. With no output schema, there are some completeness gaps.

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 implies 'ids' are MDF-e IDs via 'um ou mais MDF-e', but it does not explain 'account' or 'empresa_id', nor the exact format or constraints of 'ids'. With zero schema-level descriptions, this 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 tool exports XML of one or more MDF-e as a zip and returns a temporary download URL. This specific verb+resource+result distinguishes it from sibling tools such as hivecloud_mdfe_damdfe (PDF) and hivecloud_cte_xml (CT-e).

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 description provides clear context for when to use this tool: to obtain XML download URLs without altering the document. It also notes a prerequisite (mdfe_tenant_id in the connection), but does not explicitly name alternatives or say when not to use it. This is clear context without exclusions.

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