tealfabric_delete_process_step

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

No annotations are provided, so the description carries the full behavioral burden. It does not say the deletion is irreversible, what happens to a step referenced by a running process, whether dependencies/child references are cleaned up, or what permissions are required — all critical for a destructive operation.

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?

One short sentence with the target and key front-loaded and zero filler. Nothing is padded or redundant.

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, unannotated tool with no output schema, the definition says nothing about failure modes, cascade effects, or confirmation semantics. The agent has no basis to predict what a successful or failed call looks like.

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% with a single required string parameter, so the schema already documents step_id. The description only restates the identifier without adding format, source, or caveats (e.g., where to obtain the step_id). Baseline 3 applies.

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 resource (process step) and the lookup key (step_id). It is clearly distinguishable from create_process_step/update_process_step/get_process_step. It stops short of naming those siblings explicitly, so it settles at 4 rather than 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?

The description gives no guidance on when to delete versus retiring a process or updating a step, and no prerequisites or warnings. An agent must infer entirely from the tool name which of the many process-step siblings to call.

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