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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds nothing behavioral beyond that — no pagination behavior (despite default pageSize=50 and pageNumber), no note on result limits, ordering, or whether it fails outside the caller's organization. It essentially restates the tool's purpose.

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, front-loaded sentence with zero filler; the core action comes first and the filter qualifier follows. Nothing needs trimming.

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 five-parameter list tool with no output schema and no annotation detail beyond read-only, the description is minimal but workable — the agent knows what it returns conceptually. It leaves pagination semantics, the default 50/100 cap, and the required organizationId's role entirely to the schema.

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 0%, so the description carries the burden, and it only alludes to two of five parameters (locationId, coachId as filters). The required organizationId and the pagination parameters (pageSize, pageNumber) receive no explanation of format, scope, or effect.

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 ('List an organization's clients') and scopes it to an organization, which is more precise than a generic list. It does not, however, distinguish itself from the sibling list_clients or list_clients_needing_onboarding, so an agent must infer which listing applies.

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?

The phrase 'optionally filtered by location or coach' implies the useful context (org-wide roster with optional narrowing) but never states when to choose this over list_clients or what permissions/membership are required. Usage is implied rather than directed.

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