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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's 'Get' is consistent. It does not add any additional behavioral details (e.g., error handling, return size, null when not found), but given the annotations cover the safety profile and the output schema covers return shape, the description meets the lower bar set for annotated tools.

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 description is a single, tightly worded sentence with no fluff. It places the core action ('Get') and target resource upfront, and it is exactly the length required for this simple tool.

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?

For a tool with only one required parameter, existing output schema, and annotations that clearly mark it read-only, the description is sufficient. It could briefly mention behavior when id does not exist or the source of the id, but those gaps are minor given the overall structured metadata.

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% – the id parameter is fully described with its type and source ('Reservation id, from list_reservations'). The description 'by id' adds no new meaning beyond the schema, 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 clearly states the verb 'Get', the resource ('a single reservation'), and the specific scope ('by id'), which distinguishes it from the sibling 'list_reservations' and other get_* tools. An agent can immediately understand what this tool does 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?

The description provides no explicit guidance on when to use this tool versus alternatives. The parameter description mentions 'Reservation id, from list_reservations', but the tool description itself does not explain how to obtain the id or when one would need this over a list/filter approach.

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