Delete news

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

Despite the destructiveHint annotation already flagging danger, the description adds critical behavioral details: the entry and all comments are removed permanently, API v3 offers no undo or trash, the 'manage news' permission is required, and 403 vs 404 error meanings are explained. This goes well beyond the annotation.

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 description is well-organized with a clear lead sentence, usage context, return value, pitfalls, and cross-references. Every sentence adds value and there is no redundant fluff—the length is justified by the density of useful information.

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 destructive nature and availability of an output schema, the description covers all essential context: when to use, what happens (permanent deletion, comments removed), permission requirements, error interpretation, and related sibling tools. It is complete for a responsible AI agent to invoke safely.

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 already provides thorough descriptions for both parameters (confirm must be true, news_id should be read back from get_news), achieving 100% coverage. The description itself adds no additional param-specific meaning beyond the schema, so it matches the baseline for high schema coverage.

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 begins with a clear, specific verb and resource: 'Permanently delete a news entry.' It also distinguishes the tool from its sibling update_news, explicitly positioning delete_news as the irreversible action for mistaken or wrong-project announcements.

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 description provides explicit when-to-use guidance: use for an announcement 'published by mistake or in the wrong project.' It names the alternative, update_news, for outdated but real announcements, and cross-references list_news/get_news for retrieving the id and can_manage permissions.

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