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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description correctly doesn't repeat those. It adds genuine behavioral context beyond the annotations: times are local to the place they happen, and each booking id feeds the update/delete 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?

Two sentences, front-loaded with the core action and then expanding into a compact, useful enumeration of contents and caveats. Every sentence earns its place with no filler or redundancy.

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 one-parameter read-only tool with no output schema, the description names the expected payload categories, the timezone convention, and how the returned booking ids are consumed by sibling tools. This is sufficient for an agent to call the tool and interpret the result.

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%, including that trip_id comes from list_trips, so the baseline is 3. The description doesn't add parameter-specific detail beyond the schema, but none is needed for a single, well-documented uuid parameter.

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 the specific operation 'Get one trip' and precisely defines its scope: one trip with everything booked on it, naming the categories (flights with segments, hotels, car rentals, trains, and plans). This clearly distinguishes it from list_trips and the mutation siblings.

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 gives clear context for use: retrieve a single trip with full booking detail, and the booking ids it returns are required by update_booking and delete_booking. It doesn't explicitly name alternatives or say when not to use it, so it falls just short of full routing guidance.

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