get_top_10_mining_pools_rank

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

The description discloses that the tool returns detailed metrics in string format, including pool name, rank, blocks mined, percentage, and grand total. This covers behavioral traits beyond the implicit read-only nature; no annotations are provided to rely on.

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 concise with six sentences, starting with purpose, then listing return details, and ending with use cases. Every sentence adds value, though it could be slightly more structured.

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 presence of an output schema, the description adequately explains what is returned and when to use the tool. It covers the essential aspects for a simple data retrieval tool without missing key 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 input schema has zero parameters, so schema coverage is 100%. The description adds value by explaining what the tool returns, which is more than the schema provides.

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 explicitly states 'get the ranking of the top 10 Bitcoin mining pools based on the number of blocks mined,' providing a specific verb and resource. It distinguishes itself from siblings like 'get_mining_pool_by_slug' by focusing on a ranked list of top pools.

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 lists clear use cases: understanding mining centralization, identifying dominant pools, and analyzing hashrate distribution. While it doesn't explicitly mention when not to use it or alternative sibling tools, the context is sufficient for appropriate selection.

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