purge_celery_queue

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

With no annotations, the description carries the full behavioral burden. It clearly discloses that all pending tasks are removed, that already-executing tasks are not affected, and that the action is destructive via the caution. It does not state permission requirements or whether the purge is reversible.

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 three short sentences and front-loads the action and scope. The caution sentence reinforces the destructive nature without excessive length. Every sentence contributes useful information or emphasis.

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 tool is a destructive, parameterless queue purge with no annotations and an output schema, the description covers the essential behavior and side effect on running tasks. It could mention irreversibility explicitly, but the warning and output schema make it sufficiently complete for invocation.

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, so the baseline of 4 applies. The description adds no parameter information because there are none to explain, and the empty schema is fully consistent with the described action.

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 (Purge), resource (Celery tasks), and scope (all pending from the queue). It implicitly distinguishes from the sibling purge_celery_task by saying ALL pending tasks, but does not name the sibling explicitly. This leaves a slight ambiguity an agent might need to resolve via schema inspection.

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 warns to use with caution, but does not explain when to use this tool versus alternatives such as purge_celery_task. No prerequisites or conditions for selection are provided. The caution is a safety note, not usage routing guidance.

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