news_publisher_set_beat_config

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 that the underlying API is retired, that calls return 410 Gone, and that the domain has migrated to on-chain governance. That is precisely the behavioral fact an agent needs to avoid a wasted 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?

Front-loaded with the deprecation marker, followed by the reason and the replacement in two tight sentences. The closing tip about earning_opportunities is only loosely related to this tool and is the one element 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 retired, zero-parameter tool with no output schema, everything an agent needs is present: status, cause, and the correct next tool. Nothing material 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 for the description to add regarding inputs, and it correctly does not attempt to.

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 states exactly what the tool used to do (configure a beat via the aibtc.news API) and immediately establishes its current status as non-functional (API shut down, 410 Gone). It also names the replacement, legion_status, so the agent can distinguish this tool from its live siblings without further inspection.

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 a named alternative and a starting point ("start with legion_status"). No inference required; the routing instruction is unambiguous.

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