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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds the non-obvious default that archived audiences are excluded unless explicitly requested — behavior that is not encoded anywhere in the schema (the archived property carries no default and no description).

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 short sentences, each carrying distinct information: what the tool returns and how the most surprising parameter behaves. Front-loaded and free of filler.

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 read-only list tool with a well-documented 8-parameter schema and full annotations, the description covers what structured fields do not: the archive-exclusion default. Remaining gaps (pagination shape, return payload) are either in the schema or low-stakes given there is no output schema.

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 coverage is high (88%), so the baseline would be 3. The description earns above baseline by documenting the semantics of the one undocumented parameter, archived, whose enum values 'true'/'false'/'all' are otherwise unexplained and whose default is silent in the schema.

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 audiences') plus the scope ('in the workspace'), which an agent can distinguish from get-audience or list-audience-subscribers by name alone. It doesn't explicitly name what it is not, but the collection-vs-single distinction is unambiguous.

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 archived sentence implies the default listing behavior (active audiences only) and tells the agent that archived records exist behind a flag, which is a usage-relevant condition. It stops short of naming alternatives such as get-audience for a single record or list-audience-subscribers for members.

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