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

Annotations already declare readOnly, idempotent, non-destructive, so safety disclosure is covered and the bar is lower. The description adds genuine value beyond the annotations by disclosing the shape of the result (id, name, sample count) and the relationship to the create_* tools. It omits ordering/pagination behavior, keeping it short of a 5.

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 sentence with no filler, front-loaded with the verb and resource and ending with the useful cross-tool linkage. Every clause earns its place.

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 zero-parameter list tool with rich read-only annotations, the description covers identity, the consuming tools, and the returned fields in lieu of an output schema. It stops short of stating whether all profiles are always returned or how they are ordered, a minor remaining 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?

The tool takes zero parameters, which is the baseline-4 case; there are no parameter semantics to explain. The description does not need to add anything here and correctly refrains from inventing options.

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 ('List') and a precisely-scoped resource ('saved brand voice profiles'), and even names the returned fields. It also distinguishes itself from siblings by noting these profiles are the inputs consumed by the create_* tools, so an agent can tell it apart from the create/get tools immediately.

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 'available for the create_* tools' implies this is a lookup to perform before invoking create_from_transcript/create_from_url, which is meaningful workflow context. However, it never explicitly says when to call it, when not to, or what to do with the result, so usage remains implied rather than stated.

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