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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description usefully adds what the payload contains (contact details, period type, tags, Quarter Chase status), but says nothing about pagination, result limits, ordering, or how archived clients are treated.

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?

Two tight sentences with the returned fields front-loaded and the usage scenarios second. Nothing is repeated from the annotations or the schema, though the "Use this when:" fragment list reads slightly clipped.

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 simple read-only list tool with no output schema and no required parameters, the description does the important work of naming the returned fields and the use cases. The remaining gap is volume/ordering behavior on a potentially large client list, which an agent calling it would want to know.

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 25%, with just the "text" parameter documented as "part of a name or email". The description partially compensates by giving tag semantics through an example ("a tagged group (e.g. landlords)"), but it never explains include_archived, the standard vs calendar period_type filter, or the matching behavior of tag.

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 opens with a specific verb and resource ("Lists Clients") and enumerates the payload: contact details, period type, tags, and current-Quarter Chase status. It does not explicitly distinguish itself from close siblings like whos_outstanding, list_records, or get_client_history, so differentiation 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?

The "Use this when" clause gives three concrete scenarios: roster lookup, retrieving a Client's details, and viewing a tagged group with Quarter status. It is clear context but offers no when-not guidance or named alternative (e.g., use whos_outstanding for chase-only views).

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