Delete Recipes Bulk Actions Export Purge

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

With no annotations, the description carries the full burden and discloses the destructive scope: it removes all exports data and also cleans up orphaned files on disk. It does not mention irreversibility or permissions, but the core behavioral traits are clearly stated.

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 a single, front-loaded sentence with no filler. Every word contributes to the action, scope, and the key hidden behavior of removing orphaned disk files.

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 destructive operation with no required parameters and an output schema, the description is mostly complete: it states what gets deleted and the extra orphaned-file behavior. It omits explicit irreversibility or scope caveats, but 'Remove all' and the 'purge' title convey the destructive intent.

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 only parameter, accept-language, has zero schema description coverage and the tool description does not mention it at all. The parameter is optional and conventional, so the impact is limited, but the description adds no semantic value beyond the raw schema.

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 a specific verb and resource: 'Remove all exports data'. It also adds a distinguishing detail about deleting items on disk without a database entry, which separates it from sibling list/create/download export tools.

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 clearly implies this is the purge-all operation for exports data, but it does not explicitly name alternatives or state when not to use it. The scope ('all exports data') provides some implicit guidance, but no direct routing.

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