booking_pages_update

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

With no annotations, the description must fully convey behavior. It discloses the write scope, partial update behavior, and nested field replacement ('Nested fields... accept JSON and replace the previous value'). However, it lacks details on success responses, error handling, or rate limits, which are important for a mutation tool with 21 parameters.

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, each serving a purpose: purpose, scope, and update semantics. No redundant information, and the most critical fact (update by ID) is front-loaded.

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 21 parameters, no output schema, and no annotations, the description is too sparse. It does not explain return values, failure modes, or constraints like field optionality beyond the schema. The nested field explanation is helpful but does not compensate for the lack of broader context.

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 description coverage is 0% for 21 parameters. The description only adds meaning for nested fields ('availability, --custom-questions, --duration-options') noting they replace previous values. This is insufficient for the vast majority of parameters, leaving agents to infer their purpose from names alone.

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 'Update an existing booking page by its event type ID.' This specifies a distinct verb and resource, differentiating it from siblings like 'booking_pages_create' (create) and 'booking_pages_get' (read).

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 indicates when to use (update by event type ID) and notes partial updates: 'Only fields you pass are updated.' It also mentions required scope. However, it does not explicitly exclude scenarios or reference alternatives, but the context is sufficient for most use cases.

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