news_publisher_compile_brief

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

With no annotations, the description carries the full burden and does disclose the crucial trait: the backing API is shut down and would return 410 Gone. It stops short of saying what an actual invocation returns (handler-level error vs. success-shaped stub), which is the only remaining unknown.

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 deprecation warning is front-loaded with a visual marker, and the replacement path follows immediately. The trailing 'Tip' about earning_opportunities is only loosely related, but it is a single short sentence and plausibly useful routing.

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 deprecated, zero-parameter tool with no output schema, everything an agent needs is present: deprecation state, cause, replacement, and a fallback suggestion. No ambiguity about whether to call it.

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 input schema has zero parameters, so the baseline applies; nothing about parameters needs explaining and the description correctly implies a no-argument call.

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 did (compile the daily brief via the aibtc.news API) and its current status (deprecated, backend returns 410 Gone). An agent immediately understands this is a dead stub and what replaced it.

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 (⛔ do not use) plus a concrete alternative and even an entry sequence: legion_conclude, starting with legion_status. No inference required.

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