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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe, non-destructive read operation. The description adds specificity that it lists 'audience communities contributing to crypto attention', which clarifies the scope beyond the annotations. No contradictions are present.

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 sentence of 7 words, which is concise and to the point. It front-loads the verb and resource. However, its brevity means it lacks detail that could add value, but it is not verbose.

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?

Given the low complexity (1 optional parameter, no required params, output schema present), the description is minimally adequate. The output schema likely covers the return structure, and annotations cover safety. However, the description could explain what 'audience clusters' are or how the 'universe' parameter affects results. For a simple tool, it is sufficient but not thorough.

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%, so the schema already documents the 'universe' parameter with enum values and a description. The description adds no additional parameter semantics beyond what the schema provides, such as default behavior (default: crypto) which is not in the description. Baseline 3 is appropriate since the schema carries the full burden.

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 the verb 'list' and the resource 'audience clusters', but qualifies it with 'contributing to crypto attention', which narrows the scope and distinguishes it vaguely from siblings. However, it does not fully clarify what 'clusters' are in this context, and the sibling tools like 'list_projects' or 'list_topics' suggest overlapping listing functionality. The description is clear but lacks distinctiveness from other list tools.

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 implies this tool is for retrieving audience clusters related to crypto attention, and the input schema hints at filtering by 'universe' (crypto or tradfi). However, there is no explicit guidance on when to use this tool versus alternatives like 'list_intel' or 'list_projects'. No when-not-to-use or alternative suggestions are provided.

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