resolve_prepare_destructive_action

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

The description reveals that the tool returns a one-use token with a five-minute expiry, which adds value beyond the annotations. The annotations (readOnlyHint=true, destructiveHint=false) align with the description of a preview/validation operation.

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 a single clear sentence with no extraneous words. It is appropriately concise but could be slightly improved by structuring the key outcomes.

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 complexity (a required enum action and a complex arguments object), the description is insufficient. It lacks details on available actions, required argument fields, and the output format, despite an output schema existing.

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 zero description coverage (0%), yet the tool description provides no explanation of the 'action' enum or the 'arguments' object fields. The agent is left without any guidance on parameter values.

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: 'Validate and preview an exact delete request' and what it returns: 'a one-use five-minute token'. It distinguishes from sibling 'resolve_execute_destructive_action' which presumably uses the token.

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 implies it should be used before a destructive action, but does not explicitly mention when to use it vs alternatives, nor provides any 'when-not-to-use' guidance. With many sibling tools, more explicit context would help.

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