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

Annotations declare readOnlyHint=false and destructiveHint=false, so the mutation profile is partly covered. The description adds genuinely useful behavior: the call fails when the toggle is unavailable, confirmation is required per call by default, it reaches other people, and a Cotlet API key with app access is needed. No contradiction with 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?

The first two sentences restate the same action ('Turn Instant Book on or off for one listing' / 'Switches the Instant Book toggle for one listing'), which is redundant. The remaining sentences earn their place by adding failure, confirmation, and auth context, but the opening is not front-loaded tightly.

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 mutation with no output schema, the description covers the safety-relevant context an agent needs: failure mode, per-call confirmation, human-reach warning, and auth requirement. Only minor gaps remain, such as no explicit return/confirmation shape.

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 100% and both parameters (listing_id, enabled) are already documented in the schema. The description implies the on/off semantics via 'turn it on or off at any time' but adds no syntax or format detail 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 on/off) and resource (Instant Book for a single listing) with clear scope. An agent can distinguish this from peerspace siblings like accept_booking_request or block_calendar_time without opening the 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?

Gives a clear failure condition (toggle not available on the listing) and routes the agent to an alternative (Request Access in Peerspace first, matching the cotlet_request_access sibling). It does not explicitly name the tool, but the context is actionable and there is no misleading guidance.

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