bulk_delete_forms

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 critical behavioral traits: the tool is deprecated, requires a specific confirmation workflow, will reject calls without proper confirmation, and is kept for backward compatibility. However, it doesn't mention rate limits, authentication requirements, or error handling details.

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 structured and concise. It front-loads the most critical information (deprecation status and alternative), then efficiently explains the workflow and current behavior. Every sentence earns its place with zero wasted words.

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 complex, deprecated mutation tool with no annotations and no output schema, the description provides excellent contextual completeness regarding its current role and usage constraints. It adequately explains the workflow and limitations, though it could benefit from mentioning what happens when the tool is called correctly (e.g., what it returns).

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?

With 100% schema description coverage, the baseline is 3. The description doesn't add any parameter-specific information beyond what's already documented in the schema. It mentions the confirmationToken requirement but doesn't provide additional context about parameter usage or interactions.

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 as a bulk deletion operation for forms, distinguishing it from sibling tools like delete_form (single deletion) and confirm_bulk_delete (confirmation step). The deprecation notice adds specificity about its current limited role in the workflow.

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, detailed guidance on when to use this tool versus alternatives. It states it's deprecated, directs users to confirm_bulk_delete instead, explains the required confirmation workflow (preview_bulk_delete → confirm_bulk_delete), and clarifies that this tool will reject calls without proper confirmation.

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