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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds the useful auth requirement ('Needs scope read:rate') and confirms the data returned, but says nothing about maximum date-range size, rate limits, or behavior for dates without an active rate.

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?

Two short sentences, front-loaded with the core purpose and followed by the prerequisite scope. No filler or repetition of the tool name.

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 usefully enumerates the returned dimensions (price, minimum-stay, CTA). It covers purpose, scope requirement, and output shape; only edge-case behavior for large or invalid date ranges 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%, so all four parameters (including the optional room_type_id filter) are already documented in the schema. The description adds no extra semantic detail such as date ordering rules or whether room_type_id narrows versus aggregates results, so baseline 3 applies.

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?

States a specific verb ('Get') and a concrete resource with enumerated attributes: day-by-day price, minimum-stay rules, and closed-to-arrival restrictions for one rate type over a date range. This is clearly distinct from siblings like get_rate_type (metadata) or get_availability, though it does not name those siblings explicitly.

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 implies when to use it by describing the returned data, and adds the required scope 'read:rate' as a precondition. However, it never says when to prefer this over get_availability, get_inventory, or get_rate_type, nor any exclusions or limits.

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