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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the 'Risco: read · Efeitos: Nenhum' line adds little. What does add value is the 'Escopo: reservations:read' auth scope, which the schema does not expose. It omits real behavioral facts an agent needs: whether the panel aggregates for the given date only or a window, and whether unset date means today.

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?

Front-loaded and short, with the metric list up front where it belongs. The second line is largely boilerplate restating annotations (Risco/Efeitos), which spends space without adding information; only the scope token earns its place.

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?

There is no output schema, so the description correctly carries the burden of saying what comes back, and the metric enumeration does that reasonably. The critical gap is input semantics for the only parameter and the aggregation period, which an agent needs to call this 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 and the description never mentions the date parameter at all — no default, no timezone, no indication of whether it scopes 'arrivals' by check-in date only. With low coverage the description was expected to compensate, and it does not.

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?

Names a specific resource and enumerates its contents (arrivals, departures, in-house guests, dirty/clean rooms, balance due, occupancy), which makes it clearly distinguishable from single-metric siblings like get_occupancy_report, get_cashflow or list_balance_due. The 'equivalente ao Início do Neural' reference anchors it to a concrete product surface. It stops short of an explicit contrast with those siblings.

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?

There is no statement of when to use this composite panel versus the narrower siblings that return the same underlying numbers (get_occupancy_report, get_stays_report, get_housekeeping_status, list_balance_due). The only implied guidance is the 'Início do Neural' analogy, which assumes product knowledge the agent may not have.

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