B3TR: Apps leaderboard

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

While annotations already indicate read-only and idempotent behavior, the description adds valuable context such as mutual exclusivity of filters, supported sort fields, and cursor pagination, which are not fully captured by the schema alone.

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 three sentences with no redundancy, directly stating purpose, usage constraints, and key features. Every sentence serves a clear function.

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 read-only leaderboard tool with an output schema, the description covers all essential aspects: resource, endpoint, optional filters with mutual exclusivity, sort options, and pagination. No critical information is missing.

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 100% with parameter descriptions, but the description adds the key constraint of mutual exclusivity between date and roundId, as well as clarifying pagination and sorting behavior, going beyond the schema.

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 the action ('Get') and the specific resource ('app B3TR action leaderboard'), distinguishing it from sibling tools like getB3TRAppUsersLeaderboard and getB3TRUsersLeaderboard by focusing on apps rather than users.

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 provides explicit usage constraints (mutually exclusive roundId and date filters) and pagination details, but does not explicitly guide when to use this tool versus alternatives like getB3TRGlobalOverview.

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