news_front_page

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

No annotations are provided, so the description carries the full burden. It discloses the critical behavioral trait: the underlying API has been shut down and returns 410 Gone, meaning the tool is non-functional. This is precisely the kind of operational context an agent needs to avoid a failed call.

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 message is front-loaded with the deprecation warning and is appropriately brief. The final tip about earning_opportunities is somewhat tangential to this tool's purpose, slightly diluting focus, but it does not obscure the core instruction.

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?

Given the tool's deprecated status, zero parameters, lack of output schema, and absence of annotations, the description provides everything an agent needs: the reason it is unusable, the exact alternatives to use, and a recommended starting point. Nothing essential 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 parameter semantics are not applicable; the schema coverage is 100% and no parameters exist to describe. Baseline for zero params is 4, and the description correctly does not invent parameter details.

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 explicitly states what the tool used to do (read the compiled daily brief via the aibtc.news API) and immediately signals its current status (deprecated, API shut down with 410 Gone). It also names the replacement siblings (legion_list_stories, legion_get_story) and the starting point (legion_status), so an agent can distinguish it from all other tools at a glance.

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 guidance is unambiguous: '⛔ DEPRECATED — do not use' plus a clear redirect to legion_list_stories and legion_get_story, with a specific entry point (start with legion_status). No inference is required; the agent knows exactly when not to use this tool and what to use instead.

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