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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds valuable domain behavior beyond that: what 'Needs Attention' means (sudden compliance-rate drop) and that 'Due soon' depends on a user-configured threshold, plus the Cotlet API key access requirement. Return format is not described, but the category semantics compensate.

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?

Front-loaded with the resource and its contents, then explains the two non-obvious client categories. Slightly redundant with 'Returns what the TrueCoach dashboard shows' restating the enumerated contents, but overall tight and useful.

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 parameters, no output schema, and annotations covering the read-only profile, the description does the heavy lifting by describing the return categories an agent needs. It is nearly sufficient; only return shape/pagination is unspecified, which is minor for a fixed dashboard view.

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?

The tool takes zero parameters, so the baseline is 4. There is nothing for the description to clarify, and it correctly does not invent parameter detail.

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+resource (get the TrueCoach dashboard) and enumerates its contents: overall compliance rate, Needs Attention clients, and clients due soon. This is distinct from sibling read tools like list_clients or get_client, though it does not explicitly name an alternative it must not be confused with.

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: an agent can infer this is the tool for a holistic compliance/attention snapshot. There is no explicit when-to-use guidance, no conditions distinguishing it from list_clients or list_metrics, and no exclusions.

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