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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering safety. The description adds valuable behavioral context about the ranking methodology (accuracy vs loudness, Predictor vs Reactor), which goes beyond the annotations. It does not describe output format or pagination, but for a no-parameter tool this is acceptable. No contradictions with annotations.

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 two short paragraphs and is front-loaded with the core purpose. The second paragraph explains the scoring axis without unnecessary fluff. It is concise and each sentence contributes to understanding. No redundant repetition of the tool name or schema.

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?

With no parameters and no output schema, the description carries the full burden of explaining what the tool returns. It explains the ranking philosophy and the Predictor vs Reactor axis, but does not describe the shape of the output (e.g., list of entries with fields). Since it's a leaderboard, an agent might reasonably expect an array, but the structure is not specified. This is a minor gap, but the description is adequate for understanding the tool's purpose.

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 coverage is 100% (empty properties). Per the rubric, a zero-parameter tool gets a baseline of 4. The description does not need to explain parameters, and it doesn't introduce any confusion. It correctly omits parameter details because there are none.

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 this tool returns a leaderboard of influencers ranked by accuracy ('what people actually got RIGHT') rather than by popularity. It defines the resource and the specific ranking criterion, and the Predictor vs Reactor scoring is a distinctive feature. It doesn't explicitly name sibling tools like get_creator_rankings or get_influencer_ledger, but the purpose is specific enough to differentiate implicitly.

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 this tool (when you want accuracy-based rankings rather than reach-based ones) but does not explicitly state use cases or exclusions. No alternatives are named, and there is no guidance on when NOT to use it. The context is implied through the differentiator, but explicit routing is missing.

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