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

Annotations already declare readOnlyHint=true, and the description adds useful auth-related behavior beyond that: the token is optional under signed-in ownership and must come from manage_url when used. It does not describe error or response behavior, but for a simple read-only tool this is acceptable.

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 two sentences with no filler. The core purpose is front-loaded, and the auth nuance follows immediately. It does not repeat schema or annotation information.

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 status tool, the description covers the essential purpose and the key auth distinction. The return concept is conveyed by 'Status of a booking,' and the required parameter is inferable. It is slightly thin on response details, but those are not critical for a simple status lookup.

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%, so the description carries the burden for parameters. It adds meaningful meaning to manage_token by defining its source and optionality. However, booking_id — the only required parameter — is not explicitly explained beyond its name, and the description never states its role in identifying the booking.

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 states 'Status of a booking,' which identifies the resource and the read-only nature of the operation. It is distinct from siblings like cancel_booking and create_booking. The lack of an explicit verb such as 'get' or 'retrieve' is the only minor gap.

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 clearly explains two invocation contexts: pass manage_token from manage_url, or omit it if the signed-in user owns the booking. However, it does not name alternative tools or explicitly say when not to use this one, so the 'vs alternatives' aspect of usage guidance is missing.

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