processDefinition_deleteById

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

With no annotations provided, the description carries the full burden of disclosure. It effectively communicates the destructive scope (deletes instances, history, and jobs when cascade=true) and the error condition, though it omits reversibility or authorization details.

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?

Three tightly constructed sentences with zero waste: the first establishes the operation, the second explains the optional cascade behavior, and the third states the failure constraint. Information is front-loaded and dense.

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?

Adequate for a destructive operation with no output schema, covering the primary action, parameter behavior, and failure mode. However, it lacks details on return values, success confirmation, or authentication requirements that would be helpful given the high-stakes deletion behavior.

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?

While the input schema shows 0 parameters (baseline 4), the description adds critical semantic information about the cascade parameter (likely a query parameter not captured in the schema), explaining its boolean nature and destructive implications.

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 specific action (Delete), resource (process definition), and identifier scheme (by ID), effectively distinguishing it from the sibling tool processDefinition_deleteByKey.

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?

It provides clear operational guidance by explaining the cascade parameter's effect and explicitly stating the failure condition ('Fails if instances exist and cascade is false'), which guides the agent on when the operation will succeed or fail.

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