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

No annotations are provided, so the description carries the burden. It indicates the tool returns a ranking (not a single-item lookup) and specifies the scope (61 RWA protocols, 105+ stablecoins), which adds behavioral context. However, it doesn't disclose whether the tool reflects real-time data, whether grades are dynamic, or any limitations (e.g., staleness, completeness). It is not misleading, but could be more transparent.

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 that directly states the core function and scope. It is concise and front-loaded. It earns a 4 rather than 5 because it doesn't provide any additional context that might be useful (e.g., what 'evidence grade' means), but it avoids unnecessary words.

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 relatively simple (one optional parameter, no output schema, no annotations). The description gives the core ranking concept and universe size, which is adequate but not complete. It doesn't explain what an 'evidence grade' is or how the leaderboard is ordered (e.g., best to worst), but the grade A-F notation implies an ordering. Given the simplicity, a 3 is appropriate.

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 input schema has a single optional parameter `top_n` with a default of 15. The description does not mention this parameter at all, and schema coverage is 0%. However, the parameter name and default are self-explanatory, and since there is only one parameter, the lack of description is a minor gap. The tool's core function (ranking) makes the parameter's purpose clear.

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 states the tool ranks protocols by evidence grade (A-F) across a defined universe of 61 RWA protocols and 105+ stablecoins. It identifies the resource (evidence leaderboard) and the action (ranking by grade), but it doesn't explicitly distinguish it from sibling tools like evidence_profile or evidence_bundle, though those names imply different scopes.

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 the tool is used to get an overview of top protocols by evidence grade, which is a reasonable use case. However, it does not explicitly state when to prefer this over evidence_profile or other evidence-related tools, and it doesn't provide any exclusions or prerequisites. The context is clear enough to infer usage, but alternatives are not discussed.

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