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

With no annotations provided, the description carries full responsibility. It discloses a key behavioral trait: the data is from a compatibility sample and not reflective of current engagement. It does not mention rate limits, ordering, or response structure, leaving some transparency gaps.

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 concise sentence with no filler words. Key information about listing topic counts and the sample-source caveat is packed efficiently, making it easy to scan.

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?

This is a simple tool with one optional parameter and no output schema. The description gives the tool's purpose and a critical caveat, but lacks information about return format or how the limit is applied, though the simplicity reduces the need for extensive details.

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 sole parameter 'limit' is not mentioned in the description. Although the schema defines its type and bounds, the 0% schema description coverage means the description should explain the parameter's effect, which it fails to do.

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 'List' and resource 'topic counts' from a 'compatibility sample source', clearly differentiating it from sibling tools involving agents, permissions, and posts. The clarification that these are 'not current engagement rankings' further defines the purpose without ambiguity.

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 provides a clear context: this tool returns sample data, not live rankings, which implicitly tells users not to use it for real-time trend analysis. However, it does not name alternative tools or explicitly state conditions for use, so it stops short of full guidance.

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