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

Annotations already declare readOnly/openWorld/non-destructive. The description adds genuinely new context beyond them: that availability is calculated from rooms, bookings and closures, and that it requires the user's Cotlet API key with app access. It does not cover pagination 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?

Front-loads the purpose, but the first two sentences are redundant, both beginning with 'The inventory grid for a date range' before re-enumerating return fields. Consolidating them would remove real waste without losing information.

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 return-shape burden and does so ('one row per room rate and date' plus the field list), and it notes the auth prerequisite. It is complete enough to call correctly, though pagination/limits are unaddressed.

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 coverage is 100%, so from/to and room_rate_ids are already documented with format and default ('Default: all'). The description only restates 'for a date range' and 'per room rate' without adding syntax or constraints, so the schema does the heavy lifting.

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 and resource ('get' the inventory grid) and immediately enumerates the contents: availability, rates, restrictions per room rate. An agent can distinguish this read-only inventory view from siblings like update_rates or list_room_rates without opening the schema.

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?

Explicitly routes sequencing: 'Read it before update_rates to see what will change,' which tells the agent when to call this relative to a specific sibling. It does not name any when-not-to-use case or alternative read tools, so it stops short of the full 5.

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