update_schedule

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

With no annotations, the description carries full burden. It only mentions the PATCH method, implying partial updates, but fails to disclose any behavioral traits such as authorization needs, rate limits, side effects on existing bookings, or what happens if no fields are provided. This is insufficient for a mutation 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 a single sentence with no wasted words, front-loading the action (Update) and the method (PATCH). It is very concise, though it could be slightly more structured with additional context.

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 tool has 5 parameters, one required, and an output schema, the description is too brief. It does not explain the return value, the effect of setting is_default, or how the schedule array is structured. The schema provides some details, but the description should compensate for missing 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?

The input schema has 100% coverage with descriptions for each parameter. The description adds the 'send only fields to change' hint, which reinforces PATCH semantics but does not add meaningful detail beyond the schema. Baseline 3 is appropriate.

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 a schedule' with the PATCH method hint, which is a specific verb+resource pair. It naturally distinguishes from sibling tools like create_schedule, delete_schedule, and get_schedule.

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 includes 'send only fields to change' which provides a usage hint for partial updates. However, it does not explicitly state when to use this tool versus create_schedule or delete_schedule, nor does it mention prerequisites like having an existing schedule_id.

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