get_leaderboard

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

No annotations provided; description is adequate for a read operation ('Get') but does not explicitly state read-only, rate limits, or caching behavior. Minimal behavioral disclosure beyond what is implied.

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 focused sentences: first defines purpose and output, second gives pagination guidance. No filler, well front-loaded.

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?

Adequate for a simple list tool with no output schema and well-documented parameters. Could optionally mention ordering or default behavior, but not necessary.

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 covers 100% of parameters with descriptions; tool description only adds 'Use offset to paginate', providing minimal extra value. 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?

Clearly states the action 'Get' and the resource 'MCSR Ranked global leaderboard'. Lists returned fields (rank, ELO, tier, country, phase points), distinguishing it from sibling tools like get_player or get_match.

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?

Includes pagination hint 'Use offset to paginate', but lacks explicit when-to-use or alternatives. Context with siblings implies this is for global ranking, but no direct guidance.

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