Get booking

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered; the description earns credit by enumerating exactly what the response contains (arrival window, providers, price breakdown fields, provider pay). It does not mention permissions or rate limits, but for a read tool that is a minor gap.

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?

Front-loaded summary sentence followed by one elaborating paragraph listing returned fields. Structure is good, though 'price breakdown' and provider pay are restated across the two sentences, a small 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?

With no output schema, the description carries the burden of explaining return content and does so thoroughly — customer, address, providers, service parameters, notes, price components and provider pay. It lacks an explicit pointer to list_bookings for enumeration, which is the only notable gap for a 1-parameter read 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 100% and the single parameter already documents 'Booking id from list_bookings', so the schema does the heavy lifting. The description adds only 'by id' framing, which is already implied by the required booking_id field — baseline 3.

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 ('Reads a booking by id') and the leading line 'One booking with its price breakdown...' makes clear this returns a single record, implicitly distinguishing it from list_bookings. It stops short of explicitly naming the list sibling as the alternative, so sibling differentiation is inferred rather than stated.

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: an agent gathers it should call this when it has a booking id. There is no explicit when-to-use, when-not-to-use, or naming of alternatives such as list_bookings for enumeration.

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