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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the meaningful detail that lookup requires pairing a reference with the guest email, implying email acts as an access check. It says nothing about behavior on no-match, error cases, or what is returned.

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 front-loaded sentence with no filler; the qualifier 'made through iQuota' is placed before the parameter mention, so the agent gets scope first.

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 two-parameter read-only lookup with annotations covering safety and no output schema, the description is minimally sufficient but omits the return shape and the failure mode when the reference and email don't match, which an agent would benefit from knowing.

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%, so the description carries the burden, and it does mention both inputs ('its reference and the guest email'), implying they must correspond. However it adds no format, casing, or matching-rule detail, so it only marginally compensates for the undocumented schema.

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 ('look up a booking') and scopes it to bookings made through iQuota. It doesn't explicitly distinguish itself from siblings like get_hotel or cancel_booking, but the resource and system qualifier make its domain clear enough to route to.

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?

No when-to-use guidance, no prerequisites beyond the parameters, and no mention of alternatives (e.g., how it differs from search_hotels or when a booking lookup rather than a cancellation flow is appropriate). Usage is only inferable from the tool name and required fields.

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