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

The description goes well beyond the annotations by detailing state-dependent behavior, instructing that entry_urls must be 'presented exactly as given' and that booking navigation should occur 'on the user's behalf.' It also mandates re-showing claim_url to the human, which is critical behavioral context not captured by readOnlyHint, openWorldHint, or destructiveHint.

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 front-loaded with the core purpose and then efficiently conveys conditional outputs and action rules. It is somewhat dense, but every clause earns its place and no content is redundant with the schema or annotations.

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?

The description covers both output states, the handling of entry_urls, and the claim_url requirement, which is substantial given no output schema. However, it omits guidance on what grant is, how to handle polling intervals or errors, and what status/eta values may look like, leaving meaningful gaps for a tool with sparse 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 0%, and the description does not explain what trip_id or grant mean or how to obtain them. While trip_id is somewhat inferable from 'planned trip,' grant is entirely opaque and could prevent an agent from correctly constructing the call.

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 opens with a specific verb and resource: 'Poll a planned trip.' It further clarifies the purpose by describing two distinct response states (while research runs vs. once delivered), which distinguishes it clearly from siblings like plan_trip, booking_options, and trip_costs.

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 implies when to use the tool through temporal cues like 'While research runs' and 'Once delivered,' so an agent can infer it is used to monitor an in-progress planning flow. However, it does not explicitly name alternatives or state when not to use this tool versus siblings such as trip_costs or open_booking.

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