List leaderboards

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

Adds the login requirement beyond what annotations provide (readOnlyHint, openWorldHint). Description is consistent with annotations; no contradiction. Could mention result size limits or pagination, but the added value is solid.

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 sentences, each adding meaningful information. No filler, concise and well-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?

Describes purpose, return value, and a prerequisite. Missing details on parameter roles (limit, search) and return structure beyond ids/slugs. Adequate but not thorough.

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 description coverage is only 33% (only projectId described). The description does not explain limit or search parameters, nor their effect. Relies too heavily on the schema without adding clarity.

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 verb 'List' and resource 'leaderboards', and explains that it returns ids/slugs for referencing in other entities. Effectively distinguishes from sibling tools like specter_create_leaderboard.

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?

Mentions a prerequisite (requires specter_login), providing context for when the tool can be used. Does not explicitly state when not to use or suggest alternatives, but the context is clear enough.

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