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

Annotations declare this is a non-read-only, non-destructive, non-open-world write, so the safety profile is already carried. The description adds real workflow context beyond that: the creator must connect Cal.com and select an event type afterward, implying a multi-step dependency. It doesn't address auth, rate limits, or reversibility, but the annotations cover the safety bar.

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 sentences, front-loaded with the action and the tool's niche, then a routing caution. No repetition of schema content and no filler.

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 write tool with full schema coverage and a done-through annotations safety profile, the description supplies the missing piece: what this question type is for, its Cal.com dependency, and the alternative to avoid. Return values aren't needed (no output schema). Minor gap: guidance on the after/position insertion parameters is left entirely to the schema.

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 schema already documents all 8 parameters, including the tricky after/position/parentId insertion semantics. The description adds no parameter-level detail, so baseline 3 applies rather than a higher score.

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 (Insert) and a specific resource (Schedule appointment question), and names the backing service (Cal.com). It distinguishes the tool from its many insert_* siblings by describing the exact question type and how it differs from date/time questions.

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?

Provides an explicit when-to-use ('Use for bookings or appointments') and a when-not-to-use with an alternative ('do not substitute separate date and time questions'). It also tells the agent what happens next (creator connects Cal.com). It doesn't cover insertion-positioning tradeoffs (after vs position) that the schema leaves implicit.

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