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

Annotations already declare readOnlyHint=true, so safety is covered and the bar for added context is higher. The description adds no behavioral detail beyond scoping words already implied by parameters: no permissions required, no pagination/size limits, no statement of what the roster contains (coach identities, attendance status).

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?

It is a single front-loaded fragment with zero padding, which is structurally fine, but it is terse to the point of under-specification rather than genuine conciseness – the brevity comes at the cost of any usage or parameter guidance.

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 tool with 33% schema coverage and no output schema, the definition should clarify the org/location relationship, the optionality of locationId, and what fields the roster returns. It does none of that, so an agent could easily call it with the wrong scope or misinterpret the result.

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 only 33% – only attendanceDate is documented ('YYYY-MM-DD'). The description's 'for one date' loosely reinforces the date and location framing, but it says nothing about organizationId or about locationId being optional rather than required, leaving the two undocumented parameters unexplained in both places.

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 phrase 'A location's coach attendance roster for one date' names a concrete resource and its scope (coach attendance, single location, single date), so an agent can tell what it retrieves. However, it is a bare noun phrase with no verb, and it never contrasts with the write-side sibling record_organization_coach_attendance, so the read/write distinction is left to inference.

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?

There is no when-to-use guidance at all: no prerequisites, no indication of whether organizationId must match the location's org, and no mention of the obvious alternative record_organization_coach_attendance (or get_gym_attendance_summary). The agent must infer everything from the name.

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