madeonsol_alpha_leaderboard

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

Annotations already denote a safe read-only operation (readOnlyHint=true, destructiveHint=false). The description adds behavioral context about data size (47,000+ records) and tier-based truncation, which helps set expectations beyond 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 sentences, front-loaded with the core purpose, and every word adds value. No unnecessary filler.

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?

While the description provides data source and tier limits, there is no output schema and the description omits what fields each wallet entry includes. Given the tool has 4 parameters, the description could be more complete about return structure.

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?

With 100% schema description coverage, the input schema fully documents all four parameters. The description does not add any additional parameter semantics, so baseline of 3 is appropriate.

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 it returns 'Top statistically profitable early-buyer wallets' and mentions scoring from a large dataset, effectively conveying the tool's purpose as a leaderboard. It distinguishes itself from sibling tools like madeonsol_kol_leaderboard by specifying 'early-buyer' focus.

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 mentions tiers (BASIC, PRO, ULTRA) and truncation, implying usage limits but does not explicitly provide when-to-use or when-not-to-use guidance. No alternatives are mentioned, leaving the agent to infer context from the tool name alone.

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