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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuine value beyond that by clarifying what is NOT destroyed (run records and output files remain), which is exactly the kind of scope-of-destruction context an agent needs before a delete.

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?

Two short sentences, zero filler, with the destructive scope stated first and the non-destructive consequence second. Fully front-loaded.

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 delete with no output schema and mostly-covered params, the description conveys what is destroyed and what survives, which is the essential missing piece. It omits error/permission behavior but nothing an agent critically needs to invoke it correctly.

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 67%: deviceId and workSessionId are documented in the schema, while workflowId has no schema description. The description names workflowId as the deletion key and frames it as the caller's own definition, adding marginal meaning, but does not compensate for the undocumented workflowId semantics.

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?

States a specific verb (Delete) and a precisely scoped resource ('this caller's saved definition by workflowId'), and clarifies that run records/outputs are unaffected, which separates it from a run-cancellation tool. It doesn't explicitly name a sibling to contrast with, so it falls short of 5.

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?

Usage is implied by the scope (delete the saved definition), but there is no explicit when-to-use, when-not-to-use, or routing to alternatives such as cancel_workflow or remove_path for stopping runs or clearing files. Adequate minimum, no exclusions.

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