Bulk delete workflows

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the safety profile is partly structured. The description adds real value beyond them by disclosing that execution histories are destroyed with the workflows, the Plunk v0.12+ prerequisite, and that it asks for confirmation before running.

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?

Front-loaded with Purpose and tightly grouped under labeled sections, each sentence carrying distinct information (scope, alternative, return, trigger, prerequisites). The label-heavy formatting is slightly verbose but wastes no 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?

For a one-parameter destructive tool with no output schema, the description covers scope, alternative, prerequisites, confirmation behavior, and what gets destroyed. The 'Returns: The outcome of the batch' line is vague, but return detail is not strictly required here.

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 description coverage is 100% and the single ids parameter is fully documented in the schema (UUIDs, max 1000). The description's 'up to 1000' mirrors the schema's maxItems rather than adding new semantics, so baseline 3 is appropriate.

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), resource (workflows), and scope (up to 1000, including their execution histories). It explicitly names the sibling it is not (plunk_delete_workflow) so an agent can distinguish the bulk case from the single case without opening either schema.

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?

Provides an explicit 'Not for' exclusion naming the alternative tool and a 'Use when' condition ('clearing out abandoned automations'). When-to-use and when-not-to-use are both covered, leaving nothing to inference.

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