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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, covering safety. The description adds no extra behavioral traits beyond the ecosystem and trading context, which is acceptable given the strong annotation coverage. No contradiction exists.

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 redundant words. It front-loads the key identifying information (ecosystem and purpose) and avoids filler, making it highly efficient.

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 simple read-only nature, rich annotations, and fully documented schema, the description is adequate. It doesn't detail the return format, but no output schema exists and the tool is straightforward. The pagination and sort options are already in the schema, so the description's brevity is acceptable.

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 all four parameters having meaningful descriptions. The tool description adds no additional parameter semantics, but the schema is sufficient, so the baseline 3 applies.

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 an 'Emblem ecosystem trading leaderboard', specifying the resource (leaderboard) and scope (Emblem ecosystem). It distinguishes from sibling leaderboard tools like nansen_pnl_leaderboard by the ecosystem qualifier. However, it lacks an explicit verb like 'get' or 'list', relying on the tool name for action.

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 no guidance on when to use this tool versus alternatives. It doesn't mention exclusions or mention sibling tools. The only implied usage is that it serves leaderboard data for the Emblem ecosystem, but there is no explicit context or comparison to other leaderboard or ranking tools.

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