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

The description adds valuable behavioral context beyond the annotations: it mentions that the tool consolidates multiple companies in one call, resolves everything server-side, excludes canceled trips by default, and requires mdfe_tenant_id in the connection. The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which align with the description's read-only nature. No contradiction found.

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 a single, dense paragraph that packs a lot of information efficiently. It front-loads the core purpose and then adds details on filters, consolidation, and server-side processing. While it is somewhat long, every sentence adds value and there is no fluff.

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 tool's complexity (8 parameters, no output schema, no parameter descriptions), the description covers the essential aspects: what the report contains, how filters work, the multi-company consolidation, the optional billing, and the exclusion of canceled trips. It could be more complete by explaining the date format and the account parameter, but it is largely sufficient for an agent to use the tool correctly.

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 explains the purpose of key parameters: placa and motorista as filters, empresa_ids for consolidating multiple companies (omitted = all), incluir_cancelados and incluir_faturamento as optional flags. However, it does not explain the format of data_inicial/data_final or the account parameter, which are left to the schema's basic type definitions.

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's purpose: it generates a consolidated travel report (MDF-e) by period, with counts by month, rankings by plate and driver, and optional billing totals. It distinguishes itself from sibling tools like hivecloud_list_mdfes and hivecloud_get_mdfe by specifying the consolidated, analytical nature of the report.

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 on when to use the tool (for consolidated reports and answering questions like 'how many loads did plate X do in the quarter and how much did it bill'), and mentions that canceled trips are excluded by default. However, it does not explicitly state when not to use it or name alternative tools for simpler queries.

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