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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful context by stating the required scope (reports:read) and clarifying that forecasted revenue is separated from received payments, but it does not add details like pagination, defaults, or rate limits.

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 short and front-loaded: the first sentence lists the metrics and breakdown, the second clarifies forecast versus received revenue, and the final line states scope and risk. There is no wasted narrative, and the most important information appears first.

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 names the returned metrics and the by-property breakdown, which is important because there is no output schema. However, with two undocumented date parameters and no defaults or required-field guidance, the agent still lacks enough context to call the tool confidently with correct date ranges.

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% for the two date parameters, so the description must compensate. It only refers to 'do período' and does not define start_date/end_date semantics, date format, inclusivity, defaults, or which parameter controls the range.

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?

It clearly states the report content: room revenue, payments, nights sold, occupancy, ADR, and RevPAR for the period, broken down by property. This is specific enough to infer the resource, but it does not explicitly distinguish itself from sibling report tools such as get_occupancy_report or get_cashflow.

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 gives no explicit when-to-use guidance, prerequisites, or alternatives. It does not say when to choose this report over get_occupancy_report, get_cashflow, or get_stays_report, so the agent must infer usage from the metric list alone.

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