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

Beyond the annotations' destructiveHint, the description discloses the real-world side effects: approving confirms the meeting and emails the attendee the meeting address, while declining sends a 'not approved' note. It also exposes the constraint about already-passed meeting times, which is valuable behavioral information not present in 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?

The description is compact, front-loaded with the central purpose, and each sentence contributes distinct information: decision semantics, side effects, status constraints, optional parameters, and permissions. There is no filler or 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?

Given the tool's complexity, the description covers prerequisites, permissions, decision outcomes, side effects, and optional parameter behavior. Since an output schema exists, not detailing the response shape is acceptable. Nothing necessary for correct invocation is missing.

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%, so the parameters are already well documented. The description adds context about approval-time link/instructions falling back to team settings, but this is largely mirrored in the schema, so it does not substantially elevate meaning beyond the input schema.

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 leads with a specific verb and object: 'Approve or decline a pending booking request of the current team.' It clearly distinguishes the core review decision from generic status updates, and the outcomes for each decision are explicitly stated.

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 gives strong usage context: it only applies to pending bookings, past-time meetings can only be declined, and only the team owner/admin/lead owner may review. It does not explicitly name alternative sibling tools like update_booking_status, so it stops short of a full when-to-use-versus-alternatives statement.

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