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

With no annotations provided, the description carries the burden of behavioral disclosure. 'Read' indicates a non-mutating operation and 'one audience' limits scope, but the description does not say what data is returned, how missing audiences are handled, or any constraints beyond the organization scope.

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 front-loaded sentence with no filler. Every word—'Read', 'one', 'audience', 'this organization'—earns its place and contributes to scoping the operation.

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 two-parameter get with fully documented inputs, the description is minimally sufficient for selecting and invoking the tool. However, with no output schema and no mention of the returned audience structure or error behavior, the response shape is left entirely unspecified.

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 schema already provides 100% coverage with clear descriptions for both parameters, so the baseline is 3. The description adds no parameter syntax or format details; it only reinforces that the audience belongs to the active organization, which matches the schema's 'Active organization ID' description.

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 uses a specific verb ('Read'), names the resource ('one audience'), and scopes it to 'this organization,' which distinguishes it from listing, creating, updating, or deleting audiences. Even without explicitly naming a sibling, the singular 'one' separates it from commsharbor_audiences.

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 'Read one audience' establishes the retrieval context clearly and implies this tool is for fetching a single audience rather than listing or mutating audiences. It does not explicitly name alternatives or say when not to use it, but the singular/read framing gives an agent enough context to choose correctly among the sibling tools.

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