delete_all_articles

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

No annotations are provided, so the description must carry the full burden. It states 'Delete ALL articles' and warns caution, but it does not disclose behavioral details such as irreversibility, cascading effects on related data, or need for permissions. The description is adequate but lacks depth for a destructive action.

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?

Two sentences with the key information front-loaded: 'Delete ALL articles for this project.' followed by a caution. No wasted words; efficient and direct.

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 no parameters and no output schema, the description covers the basic action and a warning. However, for a bulk delete tool, more context about recovery, confirmation steps, or impact on other entities would improve completeness, especially compared to safer sibling tools.

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?

There are zero parameters and the input schema fully covers them (100% coverage). The description adds no parameter-specific information, but the action is well-described. Following guidelines, baseline is 3 for high schema coverage, and the description does not add extra parameter semantics.

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 clearly states it deletes ALL articles for this project, using the verb 'delete' and specifying the scope 'ALL articles' and context 'for this project'. This distinguishes it effectively from sibling tool delete_article (singular), leaving no ambiguity about the tool's purpose.

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 includes a cautionary note 'Use with caution' implying the tool is for bulk deletion, but it does not explicitly state when to use this tool versus alternatives like delete_article. No guidance on prerequisites or context for safe usage.

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