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

Annotations only declare destructiveHint=true; the description adds a genuinely non-obvious behavioral rule — checking out someone who was never checked in creates a record with matching in/out times — plus the default direction. It still doesn't say what happens on a duplicate check-in or what the resulting record contains, so it is not exhaustive.

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 compact sentences, front-loaded with the WRITE marker and the core action before the edge case; the trailing Breeze endpoint note is short and useful. No 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 3-parameter write tool with no output schema and only a destructiveHint annotation, the description covers action, scope, default, and the main edge case. It stops short of documenting permissions, duplicate handling, or the response shape, but nothing critical to invoking it 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 meaning beyond the enum by explaining that 'out' records when the person left and the edge-case semantics of out-without-in. person_id/instance_id get no extra narrative, which is fine since the schema already constrains them with patterns.

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 and resource ('record attendance for one person at one event instance') plus the two concrete operations it performs (check in / check out). The 'WRITE:' prefix immediately separates it from the sibling read tool breeze_list_attendance without needing to open either schema.

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?

Usage is only implied: the 'WRITE:' marker and 'check in (default)' phrasing signal this is the mutation counterpart to breeze_list_attendance, but the read alternative is never named and no when-to-use condition is given. Adequate but leaves routing to inference.

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