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

Goes well beyond the annotations by disclosing that invalid entries and admins/moderators are skipped silently, that the first 25 are processed immediately and the rest in the background, that tickets replace existing tickets, and that confirm-less calls return a preview without side effects. It also tells the agent to re-read eventee_list_participants to verify, which is exactly the post-mutation guidance an agent needs for a destructiveHint=true 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?

Front-loads the WRITE marker and the core action, then layers in gating, side effects, and pagination-in-batches details. It is dense and slightly run-on, but nearly every clause carries operative information; only the raw endpoint path is close to filler.

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 destructive, non-idempotent, no-output-schema mutation, the description covers side effects, confirm gating, silent failures, background processing, and how to verify results. Nothing an agent needs to invoke it safely is missing.

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 the baseline is 3, but the description adds real semantics: tickets replace existing ones, confirm is only required with send_email=true, and group can be set per person or as a default. It stops short of explaining the phone/company/position fields, which the schema already covers.

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?

Opens with a specific verb+resource+scope ("WRITE: add up to 100 people to the event as attendees") and states the mechanism for both existing-account and new users. It does not, however, distinguish itself from the sibling eventee_register_people, which an agent could reasonably confuse with this tool.

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?

Clearly states the conditions for the two modes: send_email=true triggers invitation emails and requires confirm: true, while omitting confirm produces a preview with nothing sent or added, plus explicit advice to ask the user to approve recipients. It lacks an explicit "use X instead when..." routing against eventee_register_people.

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