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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds only 'durable' and the 'settled' precondition; it says nothing about what happens when the reservation is unsettled, missing, or belongs to another account, nor about any rate or retention constraints.

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?

A single 13-word sentence with the scope constraint ('one settled Studio reservation') front-loaded and no filler. Nothing to trim.

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?

An output schema exists, so return values need not be described, and annotations cover the safety posture. However, with 0% parameter documentation and no error/precondition behavior, the description is only minimally complete for a lookup 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 description coverage is 0% and the description never mentions reservation_id or schema_version. The format/pattern/const in the schema are self-documenting, and 'one settled Studio reservation' loosely implies what reservation_id means, but the description does not compensate for the documentation gap on a 2-parameter required surface.

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 (Retrieve), a precise resource (durable Account Core receipt), and scopes it to one settled Studio reservation. No sibling tool deals with receipts, so differentiation is implicit rather than stated, keeping it just below 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?

The phrase 'for one settled Studio reservation' implicitly tells the agent this applies only to settled reservations, but there is no explicit when-to-use/when-not guidance or named alternative for unsettled or non-Studio cases. Usage is implied, not stated.

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