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

Goes well beyond annotations by disclosing that attendees and guests receive updated email invites, how round-robin host selection behaves, and the $0.01 per-call cost with no charge on failure. These are important side effects and billing details for a mutation tool.

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?

Front-loads the core action and is generally efficient, with four sentences that each contribute useful information. The round-robin detail is specialized but still relevant to behavior.

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?

Covers side effects, cost, and round-robin behavior, but omits how notify=false affects emails and what happens if the requested time is unavailable. For a mutation tool with no output schema and incomplete parameter documentation, this leaves meaningful gaps.

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 only 33%, and the description does not explain the notify parameter or clarify how start interacts with the booking. It adds little parameter meaning beyond the schema, especially for the undocumented notify flag.

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 and resource: "Move a booking to another free time." This clearly distinguishes it from sibling creation/cancellation tools like calendar_book and calendar_cancel.

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 context for use is clear—moving an existing booking—but it gives no explicit alternatives such as using calendar_find_times to locate free time or calendar_cancel to cancel instead. Usage is implied rather than guided.

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