purge_export_data

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

Without annotations, the description clearly discloses the destructive nature (removes all exports data including orphaned disk items). It adds behavioral context about scope, but does not mention permissions, reversibility, or side effects beyond what is 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 concise with three sentences (title, HTTP method, explanation). It is front-loaded but includes a redundant title line that repeats the tool name. Still efficient overall.

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 output schema or annotations, the description adequately explains what the tool does and its scope (removes all export data including disk items). However, it lacks information about success/failure responses, whether the operation is synchronous, or confirmation details.

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 has zero parameters, and schema coverage is 100%. Per guidelines, a baseline of 4 is appropriate. The description adds no parameter details since none exist, but does not need 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 clearly specifies the verb 'purge' and resource 'export data', and distinguishes from sibling tools like bulk_export_recipes by focusing on removal. It states the exact action and scope, including removal of items on disk without database entry.

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 implies usage for cleaning up export data but does not explicitly state when to use this tool versus alternatives like bulk_export_recipes or bulk_delete_recipes. No conditions or exclusions are provided.

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