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

Beyond the annotations, the description discloses meaningful behavioral details: evidence-only ranking, floor requirements (≥5 bonded completions, ≥3 counterparties), Wilson lower-bound ordering, and inclusion of participant IDs for further inspection. This goes well beyond the read-only/idempotent hints and creates no contradiction.

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 dense sentence that front-loads the tool's identity and then packs the relevant thresholds, ordering logic, and output detail into compact phrases. Every clause adds value and there is no redundancy.

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 parameterless read-only leaderboard with an output schema, the description covers the purpose, ranking methodology, eligibility thresholds, and output contents. Annotations already convey read-only and idempotence, and the output schema handles return-value documentation, so nothing essential is missing.

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 tool has zero parameters and the schema already covers everything, so there is no parameter burden for the description to carry. The baseline for a zero-parameter tool is 4, and no further parameter documentation is needed.

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 clearly identifies the tool as a reputation leaderboard and supplies specific ranking and inclusion criteria, which fully distinguishes it from the sibling market_* tools. Although it lacks an imperative verb, 'leaderboard' plus the detailed evidence-based criteria makes the operation unambiguous.

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 when to use the tool by defining it as the reputation leaderboard, but it does not explicitly contrast it with alternatives such as market_me or market_review. It gives the leaderboard's eligibility rules but does not state when not to use it or why this tool should be selected over a sibling.

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