bulk_delete_workflows

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly states 'Permanently deletes' and 'execution history', which highlights the destructive and irreversible nature. It also explains the 'delete_children' flag's effect on child workflows. However, it does not mention potential non-atomic behavior or error handling, though the core safety concern is addressed.

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 well-structured with a summary sentence, 'Args' section, and 'Returns' section. It is slightly verbose but each sentence provides necessary detail. The formatting aids comprehension, though it could condense the redundancy between the first sentence and the 'Args' content.

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?

The description covers the tool's purpose, parameters, return values, and destructive behavior, which is sufficient for a delete operation. It does not mention permissions, rate limits, or what happens if some IDs are invalid, but given the output schema exists and the destructive nature is clear, it is reasonably complete.

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 schema has 0% description coverage, but the description compensates fully by defining each parameter: application_name as 'Name of the DBOS application', workflow_ids as 'IDs of the workflows to delete', and delete_children with its default behavior. This adds meaning beyond the schema's bare type and title.

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 'Delete multiple workflows at once' with a specific verb and resource, and it distinguishes itself from the sibling 'delete_workflow' by including 'multiple' and 'bulk' in both name and description. It also notes the permanent deletion of workflows and their execution history, making the scope unambiguous.

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 clearly implies use for bulk deletion, but it does not explicitly mention when to use this tool versus the single-delete alternative. It provides context by noting the optional 'delete_children' behavior, but lacks explicit exclusions or alternative recommendations.

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