news_editor_check_earnings

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

With no annotations provided, the description carries the full burden and does so: it discloses that the upstream API is shut down and returns 410 Gone, so the agent knows any call will fail. It also explains the migration (aibtc.news now runs on on-chain governance).

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 blocking warning and symbol, followed by the reason and the replacement in one tight sentence. The trailing tip is short and actionable rather than filler.

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 dead zero-parameter tool with no output schema, the definition gives everything an agent needs: deprecation status, failure cause, and where to redirect. Nothing 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 takes zero parameters, so the baseline is 4; there is nothing to document and the description correctly does not invent parameter guidance.

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 the specific verb and resource ('check editor earnings'), immediately flags the tool as DEPRECATED, and names the exact replacement path. An agent can distinguish it from live siblings without opening a schema.

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 'do not use' instruction, the reason (410 Gone / API shut down), and concrete alternatives: legion_my_position with legion_status first, plus earning_opportunities as a secondary tip. This is exactly the when-not-to-use/alternative guidance the dimension asks for.

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