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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the safety profile is covered; the description adds real behavioral context beyond them: the 100-item cap, most-recent-first ordering, and the constraint that only status 'complete' profiles are usable for generation. Return-field disclosure is a bonus since no output schema exists.

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?

Three tight sentences: scope and ordering first, return shape second, actionable constraint about 'complete' status last. No filler, nothing repeated from the schema or annotations.

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 zero parameters, no output schema, and annotations already covering read safety, the description supplies everything an agent needs: the credential-scoped contents, the cap, the sort order, the returned fields, and the 'complete' status prerequisite for downstream generation calls.

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, which sets the baseline at 4. The description's listing of returned fields (id, name, status, confidence_score, sample_count) is return-value information rather than parameter semantics, so it neither raises nor lowers this dimension.

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 the voice profiles') and precisely scopes what is returned (the key's organisation profiles plus the key owner's personal ones), which distinguishes it from the singular sibling get_profile. An agent can identify the tool's role without opening the schema.

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 scope sentence makes clear when this tool applies (enumerating everything the credential can access) and implicitly routes single-profile lookups to get_profile. It does not name alternatives or exclusions explicitly, so it stops short of a 5.

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