preview_delete_item

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

With no annotations, the description must disclose the tool's behavioral traits, but it only states 'Preview deleting a list item.' It does not explicitly confirm that the operation is non-destructive, what the preview returns, or whether any side effects occur. The word 'preview' implies non-destructiveness, but this is not explicitly stated, leaving significant room for misinterpretation.

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 sentence, 'Preview deleting a list item,' with no unnecessary words. It is concise and front-loaded, making it easy to parse. The brevity is appropriate for a tool with a simple action and two parameters, though it sacrifices explanatory depth.

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 low complexity (2 params, no output schema), the description is too sparse to be complete. It lacks behavioral context, usage guidance, and parameter semantics. The agent must rely on the sibling tool names and the word 'preview' to infer that this is a safe, non-committal delete operation, which is insufficient for confident invocation.

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 two required parameters (itemId, listId) with 0% description coverage, and the tool description provides no additional meaning for these parameters. The parameter names are somewhat self-explanatory, but the description fails to clarify their roles or provide any context beyond the schema. This does not compensate for the lack of schema documentation.

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 'Preview deleting a list item' clearly identifies the action (preview delete) and the resource (list item), distinguishing it from sibling tools like delete_item (actual deletion) and preview_item_update (update preview). However, it does not elaborate on what 'preview' entails, leaving some ambiguity about the operation's exact purpose.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention that it should be used instead of delete_item to check effects before committing, nor does it reference any other related tools. An agent is left to infer usage from the sibling list and the tool name.

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