Book an appointment

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

Annotations provide readOnlyHint=false, idempotentHint=false, destructiveHint=false. The description adds essential context: 'Creates a real appointment and sends real invitations,' disclosing side effects beyond what annotations indicate. This fully informs the agent about the tool's impact.

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?

Three short, focused sentences. First sentence states the action, second provides a critical constraint, third reveals side effects. No wasted words, front-loaded with key information.

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 6 parameters (4 required), no output schema, and minimal annotations, the description covers the main purpose and a key constraint. It explains the booking flow and side effects. However, it does not detail the expected return value or explain all parameters, leaving minor 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 67% (4 of 6 parameters have descriptions in schema). The description adds value for the 'start' parameter by linking it to get_availability, but does not explain 'timezone' or 'meetingTypeId'. Since coverage is moderate, the description partially compensates but leaves gaps.

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 clearly states 'Book a slot' which is a specific verb and resource. It distinguishes from siblings like reschedule_appointment and cancel_appointment by focusing on new bookings. The reference to using start times from get_availability further clarifies its scope.

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 explicit guidance: use a start time from get_availability, and warns that booking an unlisted slot is rejected. This tells the agent when and how to use the tool effectively. It could mention alternatives for rescheduling or canceling, but the sibling names imply those use cases.

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