delete_procedure

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only says 'Delete', implying destructive action, but does not mention permanence, cascading effects, permission requirements, or return values. This is a significant gap for a deletion 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?

The description is a single concise sentence that conveys the essential information without any wasted words. It is appropriately sized for the simplicity of the tool and is front-loaded with the action and target.

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?

Given the lack of annotations and output schema, the description is not complete enough. It omits critical details such as whether the deletion is permanent or reversible, whether it affects related data, and any prerequisites. For a destructive operation, this information is essential for an agent to use the tool 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?

The input schema has one required integer 'id' with no description, and the description only says 'by ID'. This adds minimal meaning, confirming the ID is the identifier of the Procedure. While the parameter is simple and self-explanatory, the description does not compensate for the 0% schema coverage beyond this basic reference.

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') and the resource ('a Procedure') with the method ('by ID'). It effectively distinguishes this tool from siblings like get_procedure, update_procedure, and delete_procedure_task by clarifying the exact target is a Procedure, identified by its ID.

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 provides no guidance on when to use this tool versus alternatives, such as delete_procedure_task or when a procedure should be archived instead. It only states the operation without any context on appropriate use cases or exclusions.

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