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

Annotations already declare readOnlyHint and destructiveHint=false, so the safety profile is covered. The description goes beyond them by disclosing that In-Person clients have no login/account, that archived clients remain readable, and that the caller needs a Cotlet API key with app access — genuine operational context not present in structured fields.

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 front-loaded with the returned data, which is good, but the first two sentences restate the same payload ('profile, client type, groups, compliance rates... assigned programs' then 'profile fields... the three compliance rates and the programs assigned to them'). That redundancy costs a point.

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 single read tool with one fully documented parameter and no output schema, the description covers the return content, the archived/In-Person edge cases, and the auth prerequisite. An agent has enough to call it correctly, though the absence of any pagination or field-shape note is a minor gap.

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% and the single parameter (client_id) is fully documented in the schema as coming from list_clients. The description adds no format, edge-case, or sourcing detail beyond that, so the baseline 3 for schema-covered parameters 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 states a specific verb and resource ('TrueCoach: One client') and enumerates exactly what the response contains — profile fields, client type, groups, three compliance rates, due date, assigned programs. The word 'One' implicitly distinguishes it from list_clients, but it never names that sibling, so an agent must open the sibling list to confirm the pair.

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 offers useful situational context ('Archived clients can be read too', 'In-Person clients have no client account') that tells the agent when results may look odd, but there is no explicit statement of when to call this versus truecoach_list_clients or truecoach_create_client. Usage is implied rather than prescribed.

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