preview_bulk_delete

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively communicates this is a read-only preview operation (implied by 'SAFETY PREVIEW' and 'show exactly which forms would be deleted'), establishes it as a mandatory safety step before actual deletion, and specifies the human confirmation requirement. However, it doesn't mention potential rate limits, authentication needs, or what happens if no forms match the criteria.

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 perfectly concise with two sentences that each earn their place. The first sentence establishes the core purpose and safety context, while the second provides critical usage guidelines. There's zero wasted language, and the information is front-loaded with the most important safety warning.

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 preview tool with no annotations and no output schema, the description does an excellent job covering the essential context: purpose, safety role, and mandatory workflow. It clearly explains this is a preview step before actual deletion. The main gap is the lack of information about return values or output format, which would be helpful since there's no output schema.

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%, so the schema already documents all parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema. It mentions 'form details' which relates to the 'showDetails' parameter, but doesn't provide additional semantic context. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 tool's purpose with specific verbs ('show exactly which forms would be deleted') and resources ('forms'), distinguishing it from siblings like 'bulk_delete_forms' (which performs the actual deletion) and 'preview_single_delete' (which previews single deletions). The description explicitly positions this as a safety preview before bulk deletion.

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 explicit guidance on when to use this tool: 'MANDATORY: Present form details to human and require explicit "DELETE ALL" confirmation before proceeding to confirm_bulk_delete.' It clearly states this is a preview step that must be completed before invoking the actual deletion tool, and names the alternative tool ('confirm_bulk_delete') that should be used next.

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