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

Annotations already declare this as read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful behavioral context: access is limited to the signed-in shopper, and a 'requested handoff' status must not be conflated with a completed provider booking.

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 tight sentences with no wasted words. The core operation is front-loaded, and the important status caveat follows immediately.

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?

This is a simple one-parameter read tool, and annotations cover the safety profile. However, with no output schema, the description does not explain what status values may be returned or how to interpret them beyond the handoff caveat, leaving a meaningful gap for a status-checking 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?

There is one required parameter, action_id, and schema description coverage is 0%; the schema only supplies UUID type/format/pattern without semantic description. The description refers to 'one booking action' but does not explain where action_id comes from, what it identifies beyond a booking action, or how to obtain it.

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 a specific verb and resource: 'Get the status of one booking action,' scoped to 'this signed-in shopper.' It clearly identifies a read/status-check operation, though it does not explicitly differentiate itself from sibling tools such as report_action_outcome or confirm_booking.

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 implied by 'belonging to this signed-in shopper' and the caveat that a requested handoff is not a completed provider booking, which helps an agent interpret what status means. However, it does not state when to use this tool versus alternatives like report_action_outcome or any prerequisites.

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