create_booking

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

With no annotations, the description partially discloses behavior by noting billing implications. However, it does not explain side effects (e.g., calendar blocking, confirmation emails), idempotency, or error handling, leaving gaps in transparency.

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 concise: a single sentence followed by a clearly formatted parameter list. It is front-loaded with the primary action and efficiently uses bullet points, though it could be slightly more structured.

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 the lack of annotations and output schema, the description adequately covers parameter semantics but misses usage guidelines, error scenarios, and return value expectations. It is incomplete for an agent to fully assess the tool's impact.

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 description adds meaningful context beyond the schema: it specifies ISO 8601 format for 'start', IANA timezone for 'timezone', and explains the purpose of each attendee field. With 0% schema description coverage, this compensation is strong but not exhaustive.

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 an appointment' with a specific verb and resource, and includes billing context ('metered/billed by meetergo'). This distinguishes it from sibling tools like 'cancel_appointment' or 'list_appointments'.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., 'create_one_time_booking_link'). It does not mention prerequisites, such as needing a pre-existing meeting type, or when not to use it.

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