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

With no annotations, the description bears full behavioral burden. It discloses that the booking is real and requires explicit confirmation, but does not explain side effects (e.g., triggering notifications, creating records) or error handling. Adequate but not comprehensive.

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 effectively communicate purpose and usage condition. No superfluous words; front-loaded with key action and resource.

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 10 parameters (8 required) and no output schema, the description is minimal but works for a straightforward creation mutation. Lacks details on return value, idempotency, or error states, leaving some 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 80%, so most parameters are already documented in the schema. The description adds value by emphasizing the 'confirmed' parameter must be true, but this is also in the schema. No additional parameter context beyond what schema provides.

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 explicitly states 'Create a real Cal.com booking for Raze', specifying the verb (create), resource (Cal.com booking), and context (for Raze). It distinguishes from siblings like 'get_available_slots' by emphasizing that it's the final creation step.

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 clearly defines when to use the tool: 'Only call this after the visitor selected an available slot and explicitly confirmed the booking.' This provides explicit preconditions and helps avoid misuse.

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