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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, but the description adds substantial behavioral context beyond them: the exact metrics returned, the rule that some channels count toward room nights but not ADR, multi-currency conversion to the default currency, and the API key requirement. This is rich, specific, and consistent with the 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 purpose is front-loaded, but the description is longer than necessary and repeats the metric list: the opening sentence names 'reservations, room nights, ADR and cancellations,' and the next sentence repeats those plus additional metrics. The caveat and currency sentences earn their place, but the redundancy costs conciseness.

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?

With no output schema, the description carries the full burden of explaining return values, and it does so thoroughly: it lists the returned metrics, describes channel-level breakdown, notes the booking engine inclusion, explains ADR/room-night treatment, and covers currency conversion and authentication needs. Nothing essential for correct invocation is missing.

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 100%, and the schema documents all three parameters (from, to, date_basis) including the date_basis enum and default. The description adds no additional parameter semantics beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific verb and resource: it reads the Insights Booking performance report and lists the metrics returned. It is clear about what the tool does, but it does not distinguish itself from sibling report tools such as little-hotelier_get_statistics or little-hotelier_export_report, so it falls short of a 5.

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 explicit when-to-use guidance, no exclusions, and no mention of alternative tools. The closest is 'Reads the Insights Booking performance report,' which implies a reporting use case but gives no help in choosing between this and sibling report or statistics tools.

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