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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description adds genuinely non-obvious semantics beyond them: an unknown source yields source_unavailable, and a positive result neither holds inventory nor approves dogs. That prevents an agent from treating a positive check as a reservation or dog clearance. It does not mention rate limits or what a negative result contains.

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, zero waste, with the core action front-loaded and the behavioral caveats compressed into a single clause. Every phrase carries signal.

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 carries the burden of describing returns; it covers only the source_unavailable edge case and the 'no hold' guarantee. What a positive or negative availability result actually looks like, and any capacity/date-constraint rules, remain unstated for a 5-parameter availability tool.

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 60%, with check_in/check_out and dogs already documented in-schema. The description adds the notion that the stay must be 'bounded' (a range, not open-ended) and reinforces that dog approval is a separate step, but it says nothing about adults/children or date-ordering constraints, so it only partially compensates for the coverage gap.

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 ('Check a bounded stay against the live authoritative calendar') and the word 'authoritative' hints at the distinction from get_quote or get_booking_options. It does not explicitly name a sibling, so an agent must infer the split from the phrasing alone.

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?

Usage is only implied: the 'bounded stay' framing suggests this is a pre-booking availability probe, but the description never says when to call this instead of get_quote or get_booking_options, nor any prerequisite ordering. No exclusions or alternatives are stated.

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