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

Annotations already cover read-only, idempotent, and non-destructive behavior, so the description does not need to restate safety. It adds some useful context by saying the returned definition is 'owned' and contains 'pain points and channels,' but it does not describe behavior on missing IDs, permissions, or error cases. This is adequate but not rich.

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?

The description is a single, efficient sentence that conveys the resource, ownership constraint, and returned content without filler. Every phrase 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 simple one-parameter, read-only retrieval tool, the description plus schema and annotations are nearly complete. It could be slightly more explicit about what happens when the audience is not found or that it returns the full definition object, but these are minor gaps given the tool's simplicity.

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 100%, with audience_id documented as a required 'Full UUID from the matching list tool.' The tool description itself adds no parameter-level detail, but the schema already does the needed work, so the baseline score of 3 is appropriate.

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 states a specific action ('Get') on a specific resource ('one owned audience definition') and specifies the key contents ('pain points and channels'). The singular 'one' and 'owned' distinguish it from sibling list and create/update tools, so an agent can identify its 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 description gives no explicit guidance about when to use this tool versus list_marketing_audiences, create_marketing_audience, or update_marketing_audience. The only implication is that it fetches a single audience, but it does not mention how to obtain the audience_id or when the list tool should be used instead.

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