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

Annotations establish the safety profile (not readOnly, idempotent, not destructive), and the description adds the important precondition on status. It doesn't cover side effects (e.g., notifications sent, calendar updates) or error behavior when the status isn't pending, but the status constraint is meaningful context beyond the annotations.

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 short, front-loaded sentences with the action first and the constraint second. No filler, no 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?

For a single-param mutation tool with clear annotations, the description covers purpose and the key precondition. Minor gaps remain: no mention of the response on success/failure or whether the caller needs to re-fetch the booking first.

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%, so the single 'id' parameter is fully documented in the schema as a Booking UUID. The description adds no parameter-specific detail (e.g., how to find a booking ID), so baseline 3 applies.

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 (Confirm) and resource (booking), and the precondition clause ('Only works on bookings with status pending') further distinguishes it from siblings like neuron_complete_booking or neuron_cancel_booking. An agent can immediately tell what this tool does.

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?

Explicitly states the condition under which the tool works ('status pending'), which functions as a when-to-use constraint. However, it does not name alternatives for non-pending bookings (e.g., cancel or complete) or state what to do if the booking isn't pending, so it falls short of a full routing statement.

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