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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Read' signals a non-mutating operation, but nothing is disclosed about error behavior when the audience doesn't exist, what fields the response contains, whether audience members are included, or any permission prerequisites beyond the two IDs. The description adds only the minimal safety implication of 'read' and nothing more.

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?

At three words, the description has zero waste and is maximally front-loaded — the verb and resource appear immediately. It reads as a complete, grammatical utterance rather than a tautology. However, it borders on under-specification, which prevents a 5; brevity here may be cutting into content that should exist.

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?

The tool is a simple getter with two fully documented parameters, but there is no output schema and no annotations, so the description is the only source of behavioral and return-value information. It does not state what the response contains, how it differs from listing via commsharbor_audiences, or what happens on not-found. For an agent choosing among 130+ siblings — several of which operate on audiences — this is under-specified.

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% — both audience_id and organization_id have descriptions in the schema. The tool description 'Read one audience' adds no parameter-level meaning beyond what the schema already provides. Per the baseline rule, with high schema coverage, a 3 is appropriate even without additional param detail in the 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 'Read one audience' states a specific verb (read), resource (audience), and cardinality (one), which clearly implies a singular get operation. The word 'one' implicitly differentiates it from the plural sibling commsharbor_audiences. However, it doesn't explicitly distinguish itself from other audience-related siblings, and the description is so terse that it relies on the tool name for most of the differentiation.

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?

No guidance is provided on when to use this tool versus alternatives such as commsharbor_audiences (list), commsharbor_audience_members, or commsharbor_audience_update. Given the enormous sibling list (130+ tools) and several similar audience tools, the description provides no context for selection. There are no usage conditions, exclusions, or alternative references.

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