preview_single_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 describes the tool's behavior: it's a preview-only operation that requires human confirmation before any deletion occurs, implying it's non-destructive and interactive. However, it doesn't mention potential errors (e.g., invalid formId) or response format, leaving some gaps.

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 front-loaded with the core purpose in the first sentence, followed by a clear mandatory instruction. Both sentences are essential: the first defines the action, and the second specifies the required workflow. There is no redundant or verbose language, making it highly efficient.

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 tool's complexity (preview with human interaction), no annotations, and no output schema, the description is mostly complete. It covers the purpose, usage guidelines, and behavioral context (non-destructive preview with confirmation). However, it lacks details on error handling or the structure of the preview output, which could be useful for an agent.

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 100% description coverage, with 'formId' clearly documented. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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 specific action ('Preview a single form before deletion') and distinguishes it from siblings like 'confirm_single_delete' (which executes deletion) and 'preview_bulk_delete' (which handles multiple forms). It specifies the resource ('form') and the preparatory nature of the operation.

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 explicitly states when to use this tool ('before deletion') and provides a mandatory workflow: present details to a human and require explicit 'DELETE' confirmation before proceeding to 'confirm_single_delete'. It clearly distinguishes this from the execution step, offering direct alternatives and prerequisites.

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