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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: no hint about what is ranked, whether results are cached/live, how many entries are returned, or how scoring is computed.

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 words with zero waste, which is maximally concise, but the size is driven by under-specification rather than discipline. There is no front-loaded statement of action or return content beyond the bare label.

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?

With no parameters and no output schema, the description carries the full burden of explaining what the leaderboard contains, its ordering, and roughly what an agent gets back. 'Model leaderboard' leaves all of that to guessing, so it is not complete enough to call the tool confidently.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The only shortfall is that the description does not say the call is argument-free or what the implicit selection criteria are.

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 'Model leaderboard' is a noun phrase that largely restates the title 'Forge Leaderboard', only clarifying that the subject is models. It names no verb (list? get? compute?) and does not distinguish this from siblings such as forge_badge, forge_verify, or forge_delta_submit, so an agent cannot tell what the tool actually does.

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?

There is no when-to-use guidance, no exclusions, and no mention of alternatives. At best the word 'leaderboard' faintly implies a read of rankings, but nothing tells an agent why to reach for this over forge_badge or trust_score.

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