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

No annotations exist, so the description carries the full burden and does meaningful work: it discloses that the effect is reversible and that existing bookings are unaffected. It does not mention permission requirements or whether the response confirms the new state, which keeps it from a 5.

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?

One sentence, front-loaded with the action, and every clause (reversibility, effect on existing bookings) adds information. Nothing is wasted or padded.

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-parameter, no-output-schema mutation tool, the description covers the action, its reversibility, and its side effects on existing data. The only gap is that it says nothing about what is returned or required authorization, minor given the tool's simplicity.

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% and the schema itself explains that 'link' accepts a title, slug, or URL and points to list_booking_links. The description adds nothing about the parameter beyond the schema, 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 ('Turn ... off') and resource ('booking links'), and immediately clarifies the effect: no new bookings, existing bookings preserved. That phrase alone distinguishes it from delete_booking_link and update_booking_link without the agent needing to open either schema.

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 clause 'until it's turned back on (bookings already made stay)' implicitly routes the agent here instead of delete_booking_link for reversible takedowns, and instead of update_booking_link when the goal is to stop bookings entirely. It doesn't name those siblings explicitly, so it falls short of a 5.

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