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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: what population is being measured (Kellian paper traders, not Polymarket traders) and how results are grouped (per outcome, expressed as open interest). It does not discuss scope limitations such as chains probed or data freshness, which keeps it from a 5.

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?

Two sentences, zero filler. The metric list is front-loaded and the disambiguation clause follows immediately, so the reader gets scope first and the most likely confusion point second.

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?

With an output schema present, the description need not explain return values, and annotations cover the safety profile, leaving little required. What remains is covered: what the tool measures and what it explicitly does not measure. A small gap is that it never states chain/coverage behavior, though the schema field for chainId handles that adequately.

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 both 'address' (market contract address) and 'chainId' (probes enabled chains if omitted) fully documented, so the baseline is 3. The description reinforces the single-market scoping of 'address' but adds no format or behavior detail about chainId probing that the schema does not already carry.

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?

States a specific verb-resource pair ('holders of one Kellian market') and enumerates the exact metrics returned: distinct holders, verified-human count, whale count, and total shares per outcome (open interest). It also draws an explicit boundary against the smart money lists, so an agent can separate it from problee_get_smart_money without opening either 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 closing sentence gives a clear exclusion rule: this is play-money/paper-trader data, not the Polymarket smart money data, which routes the agent away from problee_get_smart_money. It stops short of naming the sibling tool directly or describing the inverse case ('use X when you want real-money holders'), so it is strong context rather than a full when/when-not/alternative triad.

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