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

It leads with 'WRITE' and discloses the underlying Breeze endpoint (GET /api/volunteers/add), which usefully flags the unusual read-verb-writes-data quirk and is consistent with destructiveHint=true. However, it does not say what happens on a duplicate assignment, whether existing volunteer assignments are replaced, or what error conditions look like.

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 tight sentences with the operation type front-loaded and the API mapping second; no filler or restatement of the title.

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 two-parameter mutation with no output schema and only a destructiveHint annotation, the description covers the write intent and endpoint but omits idempotency/duplicate behavior and error handling, leaving meaningful gaps for an agent deciding whether calling it is safe.

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 documented in the schema as numeric Breeze ids, so the schema already carries the meaning. The description reinforces the cardinality ('one person', 'one event instance') but adds no id format or sourcing detail beyond what the schema states.

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) plus resource and cardinality (one person as a volunteer for one event instance), which is precise enough to distinguish it from the list_volunteers and add_person siblings. It stops short of explicitly naming those siblings as non-overlapping alternatives.

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 says what the tool does but never says when to reach for it versus breeze_list_volunteers or breeze_add_person, nor what preconditions exist (e.g., the person and instance must already exist). No exclusions or alternatives are offered.

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