book_appointment

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

With no annotations, the description discloses critical behavioral traits: it verifies the slot first (read-before-write) and is dry-run by default, requiring confirm:true for the actual booking. This is excellent transparency for a mutating 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?

The description is two sentences, front-loaded with the core purpose, and every word adds value. It avoids fluff and is easy to parse quickly.

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?

The description covers the most important behavioral context (dry-run, verification) but does not mention return values or error handling, and there is no output schema. It also does not relate to sibling tools, leaving the agent to infer the workflow. Still, it is fairly complete for a booking operation.

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?

The schema covers 57% of parameters with descriptions. The description emphasizes the confirm parameter's dry-run behavior, but this is largely already in the schema. It does not explain the undocumented parameters (title, contactId, calendarId), so it adds limited value beyond the 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 clearly states the tool books an appointment, using a specific verb and resource. It also distinguishes from siblings like get_free_slots by noting it verifies the time is a real free slot before writing.

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?

It provides the key usage instruction to pass confirm:true to actually book, and explains the dry-run default. However, it does not explicitly mention when to use this tool versus alternatives like get_free_slots, nor does it state any exclusion criteria.

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