delete_diagram_file

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

With no annotations, the description bears full burden for behavioral disclosure. It only states 'Delete' (destructive action) but fails to specify effects (permanent deletion, permissions needed, behavior if file is open or nonexistent). Should detail side effects.

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 sentence, concise and front-loaded. It could be slightly more efficient but is not verbose.

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 tool with no annotations and a single parameter, the description omits critical context: confirmation, recovery, impact on open files, and error scenarios. Not complete enough despite low complexity.

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?

Schema coverage is 100%, but the description adds no value beyond the schema's property description ('Filename of the diagram to delete'). No extra meaning like format, path, or case sensitivity is provided.

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 'Delete a saved BPMN diagram file' uses a specific verb ('Delete') and resource ('saved BPMN diagram file'), clearly distinguishing it from sibling tools like open_bpmn, new_bpmn, list_diagrams, etc.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., close, list_diagrams) or what prerequisites exist (e.g., file must exist, permissions). The lack of when-not or context makes usage ambiguous.

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