news_leaderboard

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

With no annotations, the description carries the full burden and does so: it discloses the failure mode (API shut down, returns 410 Gone), which is the single most important behavioral trait for a dead tool. It goes beyond 'deprecated' to explain the concrete error an agent would hit.

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?

Front-loaded with the stop signal before any explanation, which is correct ordering. The trailing 'earning_opportunities' tip is unrelated to this tool's decision and is the one sentence that does not strictly earn its place.

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 zero-param deprecated stub with no annotations or output schema, this is complete: status, reason, replacement tools, and a recommended starting call. Nothing an agent needs in order to route correctly 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?

The tool has zero parameters, which sets the baseline at 4. No parameter context is needed or offered, and the deprecation notice makes parameter semantics moot.

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?

States exactly what the tool used to do (rank correspondents via the aibtc.news API) and immediately flags that it is dead and why (410 Gone). An agent can tell instantly what this tool is and that it must not be selected.

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?

Explicit when-not-to-use ('⛔ DEPRECATED — do not use') plus named alternatives (legion_status, legion_list_stories) and an ordered starting point ('start with legion_status'). Nothing is left to inference.

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