storage_delete_document

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

No annotations are provided, so the description must carry full behavioral disclosure. It mentions deletion and state removal but does not clarify permanence, side effects, or the role of the 'remove_artifacts' parameter. The description gives only minimal behavioral insight.

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: first states the action and resource, second provides usage condition. Every sentence is necessary and efficient. No redundant 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?

Given the tool has 3 parameters and an output schema, the description is minimal. It covers the primary action and usage condition but omits prerequisites (e.g., does the document need to exist?) and the meaning of 'sidecar persistence'. It is adequate but not fully complete.

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 coverage is 0% with no parameter descriptions. The description mentions 'remove persisted MCP state for a specific document' but does not explain the purpose of any parameter (path, doc_id, remove_artifacts) or how to use them. The description adds almost no value 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 specifies the verb 'delete' and the resource 'one document from local sidecar persistence'. It distinguishes from sibling tools like storage_cleanup_sidecars by focusing on a single document removal.

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: 'Use only when the user asks to remove persisted MCP state for a specific document.' It provides clear context but does not mention alternatives or when-not-to-use scenarios beyond the implied exclusivity.

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