get_booking

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

The only behavioral information is the word 'simulated', which describes the data nature, not the operation. It does not disclose read-only status, error behavior, or side effects. With no annotations, the description carries the full burden and falls short.

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?

One sentence, front-loaded with the action and scope, zero waste. The format example is embedded efficiently.

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 single-parameter retrieval tool, it is mostly adequate, but it omits any mention of the return shape or error cases (e.g., not-found behavior). Given no output schema and no annotations, a bit more detail would help, but the low complexity mitigates the gap.

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 0%, but the description provides a concrete example format 'FLM-XXXXXX' which gives the agent a template for the booking_reference parameter, adding value beyond the schema's bare type.

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), resource (booking), and method (by reference code). It clearly distinguishes from book_flight and cancel_booking based on the action.

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?

Implies usage when you have a booking reference code, but does not explicitly contrast with siblings or mention when not to use it. The condition (having a reference) is clear enough, but no alternatives are named.

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