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

The readOnlyHint annotation already establishes this as a safe read. The description adds the endpoint (/api/events/attendance/list) and the shape of returned fields, which is useful, but says nothing about pagination, result caps, or ordering for what could be a large list.

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?

A single dense sentence that front-loads the core purpose and appends the mode alternatives plus the raw endpoint. Nothing is wasted, though the parenthetical field list makes it slightly harder to parse at a glance.

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, the description usefully enumerates what comes back (person_id, created_on, check_out, or a head count), and the readOnly annotation covers the safety profile. Only pagination/limit behavior for potentially large attendance lists is left unaddressed.

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%, so each of the three parameters is already documented, including the person/anonymous enum. The description reinforces that details and anonymous are optional variants but adds no syntax or format information beyond the schema, warranting the baseline 3.

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?

The description states a specific resource (attendance for one event instance) and enumerates the returned fields (person_id, created_on, check_out) or the anonymous head count alternative. It clearly distinguishes a read of attendance from the write-side sibling breeze_record_attendance, but never names that sibling explicitly.

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 implies when to use the tool (to see who checked in to a given instance) and flags the two modes of the type parameter, but gives no explicit when-not guidance or reference to alternatives like record_attendance or get_event. Usage is inferable rather than stated.

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