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

Annotations already declare readOnly, idempotent, non-destructive and openWorld=false, so the safety profile is covered. The description adds a genuine operational guarantee beyond that — it does not start or retry creation — which matters for an agent deciding whether this call has side effects. No polling/refresh guidance is given, keeping it below 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?

Two short sentences, front-loaded with the read scope and closed with the negative side-effect guarantee. Nothing is wasted.

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?

An output schema exists, so return-value detail is rightly omitted, and the description covers scope plus the key non-mutation guarantee. It is nearly complete for a single-param read tool, lacking only any hint about progress semantics or whether repeated polling is expected.

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 0% for the single required operationId, and the description only implies it identifies 'one Audience creation operation' without naming the parameter or explaining any constraints. The format constraint lives in the schema, so this is a marginal addition — baseline 3 given one undocumented param.

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 (Read) and resource (one Audience creation operation plus members' training progress), which is distinguishable from create_audience_from_brief and list_audiences. It does not explicitly name a sibling, so it falls short of a 5.

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 clause 'Never starts or retries creation' implicitly routes the agent here for polling rather than for triggering creation, which is useful. However, no alternative tool is named and no explicit when-to-use condition is given, so guidance remains implied.

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