create_booking_page

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

Beyond the annotations (readOnlyHint=false, etc.), the description explains the booking flow: returns a booking_url, confirmed event creation on the calendar, webhook firing with booking_page_id, and that existing events always block slots. This adds significant behavioral context not covered by annotations.

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 three sentences, clearly front-loaded with the purpose. Every sentence adds essential information (what it creates, what it returns, how it works, a key constraint). No unnecessary words.

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 complexity (10 parameters, no output schema, no nested objects), the description covers the core functionality, output, and critical constraint. The schema covers parameter details, so the description is complete for the tool's purpose.

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 100%, so baseline is 3. The description adds some context about availability_constraints and the overall behavior, but does not add meaning to individual parameters beyond what the schema already provides. The return value is explained, which helps, but for parameter-specific semantics it is adequate.

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 starts with a clear verb and resource: 'Create a public booking page... for a calendar.' It distinguishes itself from related tools like create_event (creates single event) and create_proposal (scheduling proposals) by specifying it creates a hosted scheduling link. The return value (booking_url) is also mentioned.

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 states when to use the tool: to create a booking page for a calendar. It also provides context about availability_constraints and how existing events block slots. However, it does not explicitly mention when not to use it or provide alternatives, though sibling context makes this clear enough.

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