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

The readOnlyHint annotation already establishes this as a safe read, so the bar is lower. The description adds useful scope context (single event instance, and that results may be either named check-ins or an anonymous count), but says nothing about pagination, result limits, or empty-instance behavior.

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 sentence that front-loads the core answer ('who checked in to one event instance') and tucks the returned fields into a parenthetical. Every clause carries information; the Breeze endpoint reference is cheap provenance.

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 must carry return-value burden, and it does list the key fields returned. The three parameters are fully covered by the schema. The main gap is pagination/volume behavior for an attendance list, which is minor at this complexity level.

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 the schema already documents all three parameters, including the person/anonymous enum. The description's mention of 'each person's details' and 'anonymous head count instead' loosely mirrors those parameters but adds no format, default, or edge-case detail beyond the schema. Baseline 3 applies.

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 gives a specific verb (list) and resource (attendance) scoped to 'one event instance', and even enumerates the returned fields (person_id, created_on, check_out), which cleanly separates it from breeze_record_attendance. It stops short of explicitly naming the sibling it must not be confused with, but the read-vs-write distinction is inferable from 'who checked in'.

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 implied rather than stated: the agent can infer 'call this to see attendance for a given instance_id'. The 'optionally with each person's details, or the anonymous head count instead' clause describes a parameter choice, not when to pick this tool over an alternative, and no prerequisites or exclusions are given.

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