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

Annotations supply destructiveHint=true, but the description adds no behavioral detail beyond the annotations: no statement about reversibility, whether an existing assignment is overwritten, auth requirements, or duplicate handling. It only restates that this is a write and names the upstream endpoint.

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?

Two terse sentences with the operation type and scope front-loaded. No wasted 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?

For a 2-param mutation with 100% schema coverage and a destructiveHint annotation, the essentials are technically covered, but the destructive flag on a scheduling action is left unexplained and there is no note on side effects or failure modes.

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 100% and both parameters are required Breeze ids, so the schema fully documents inputs. The description adds nothing beyond the schema; baseline 3 applies.

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?

States a specific verb (schedule), resource (volunteer), and scope ('one person ... one event instance'). The 'WRITE' prefix immediately separates it from read siblings like breeze_list_volunteers.

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 'WRITE' marker and 'schedule one person' imply usage context, and it implicitly contrasts with breeze_list_volunteers. However, no explicit when-to-use vs when-not guidance or alternative is named.

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