cloudflare_worker_delete

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

Given no annotations, the description explicitly labels the tool as 'DESTRUCTIVE' and states 'cannot be undone', providing essential behavioral context. However, it lacks details on prerequisites or error conditions.

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 extremely concise—one sentence plus a label—with all information front-loaded. Every word is necessary and no fluff.

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 simple deletion tool with one parameter, the description covers purpose, parameter, and behavioral note. It lacks mention of error handling (e.g., script not found) or preconditions, but overall is reasonably complete.

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 has 100% description coverage for its single parameter. The description adds the phrase 'by name' which aligns with the schema, but provides no additional semantic value beyond the schema description.

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 the action ('Delete'), the resource ('Workers script'), and the specific parameter ('by name'). It distinguishes from sibling delete tools by naming the specific resource type.

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 when deletion of a Worker script is needed, but does not provide guidance on when not to use this tool (e.g., if dependencies exist) or mention alternative tools for similar operations.

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