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

No annotations are provided, so the description carries the full behavioral burden. It discloses the four ranking modes but says nothing about authentication, rate limits, default window, sort direction, or what the ranking output contains.

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 short, front-loaded sentences with no filler; the core ranking modes lead and the platform filter follows. Efficient, though extremely terse.

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 3-param read tool with no output schema and no annotations, the description covers the modes and the platform filter but omits defaults, valid platform values, and return shape. It is minimally viable but leaves real gaps.

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 coverage is 0%, so the description must compensate. It does map loosely to all three params ('overall, this week, rising' → window, 'inside one topic' → topic, 'platform filters by ecosystem' → platform), but gives no value formats, defaults, or accepted platform/ecosystem values.

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 ('Rank bots') and enumerates the ranking modes (overall, this week, rising, inside a topic). None of the sibling tools are leaderboard-related, so it is easily distinguishable, though it never names an alternative to route between.

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?

No explicit when-to-use or when-not guidance, and no sibling alternatives are named. The enumerated modes imply the tool returns rankings but leave the agent to infer which mode fits a given request.

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