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

Annotations only declare destructiveHint=true, so the description carries most of the burden — and it does, flagging 'WRITE' up front and explaining the resulting record semantics for the out direction. It omits auth/permission requirements and does not address idempotency or duplicate check-ins, which are plausible concerns 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?

One dense, front-loaded sentence: the operation type ('WRITE') comes first, then scope, then the mode semantics. Every clause carries information; nothing is padding.

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?

With no output schema and only a destructiveHint annotation, the description supplies the write semantics and mode behavior an agent needs to call it correctly. It lacks any note on permissions or failure modes, which would round out a mutation tool description.

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 meaning beyond the schema by explaining that 'out' records when the person left and what happens if they were never checked in — behavior the enum description alone does not convey.

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 (record attendance), the resource (attendance for one person at one event instance), and the two modes (in/out). It is clearly distinguishable from the sibling breeze_list_attendance, which reads rather than writes.

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?

It establishes the default (in) and the non-default (out) plus a non-obvious edge case (checking out someone not checked in creates a record with matching in/out times). It doesn't explicitly name when to prefer this over other write tools like breeze_add_event, but the scope is narrow enough that context is clear.

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