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

With no annotations, the description carries the burden of behavioral disclosure. It adds one meaningful behavioral fact: account balances are private and never shown. However, it omits other useful traits such as read-only behavior, whether results are real-time, response structure, or any limits/errors.

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?

A single sentence front-loads the primary purpose and packs the sort options, defaults, and privacy restriction into a compact, easily parsed format. There are no wasted words or redundant restatements of the tool name.

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 low-complexity tool with two optional parameters, the description covers the purpose and the sort field. However, since there is no output schema, the agent cannot fully anticipate the response shape, and the meaning/range of 'limit' is not disclosed, leaving notable gaps despite the simple nature of the tool.

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 0%, so the description must compensate. It restates the sort enum and default from the schema, adding the 'by performance' context, but it does not explain the limit parameter or define the metrics. This partial compensation is helpful but leaves one parameter semantically under-specified.

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 identifies the resource (leaderboard) and its core purpose: ranking top agents by performance, with three sort dimensions. It lacks an explicit verb like 'list' or 'get' and does not name a sibling tool to differentiate it, but the intended function is unambiguous.

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 usage for viewing agent rankings and offers sort choices, but it does not state when to prefer this tool over siblings such as my_ledger, mesh_stats, or task tools. There are no explicit exclusions, alternatives, or contextual cues beyond the obvious leaderboard purpose.

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