Delete document

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

With no annotations provided, the description carries the burden of behavioral disclosure. It transparently explains that a backup is made first, the file is then removed, and invalid inputs are refused. It does not mention return values on success/failure or backup failure handling, but the key behavioral traits are covered.

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?

Two sentences front-load the primary action and then add critical safety/backup details. Every sentence earns its place with no repetition of schema information.

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 deletion tool with no output schema and no annotations, the description adequately covers purpose, safety, and backup. It omits details about return values or error responses, but these are less critical for such a simple operation.

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 100% coverage for the single parameter, and the schema description already states the filename is in the Resumes folder. The tool description reinforces that paths outside the folder are refused, which adds a little context, but overall it does not significantly go beyond the schema.

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 a saved document from the Resumes folder' with a specific verb and resource. It distinguishes itself from sibling document tools (list, read, save, print) by focusing on deletion and exclusively referencing the Resumes folder.

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 context is clear: the tool is for deleting saved documents in the Resumes folder, and it adds a safety note about refusing paths outside that folder. However, it does not explicitly mention when to prefer this over other delete tools (e.g., delete_job, delete_column), though the resource type makes it obvious.

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