delete_item

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

The description discloses that the item is 'permanently removed,' which goes beyond the destructiveHint annotation by specifying permanence. It also explains the use of condition_expression for existence checks, adding behavioral context. No contradiction with annotations.

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 well-structured with a clear opening sentence, a note on permanence, and separate usage sections. Each sentence provides value, and the format is easy to scan. It is appropriately sized for the tool's complexity.

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?

The description covers the tool's purpose, usage conditions, alternatives, and return value ('JSON confirmation with the deleted item's key'). This is comprehensive given the annotations and schema, leaving no major gaps for an agent to invoke it correctly.

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 description explicitly mentions condition_expression and its purpose, adding meaning beyond the schema. It also references 'primary key' and 'DynamoDB table,' which aligns with key and table_name parameters. However, it doesn't elaborate on all parameters, relying partly on the schema's existing descriptions.

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 function: 'Delete a single item from a DynamoDB table by its primary key.' It uses a specific verb (delete) and resource (single item), and distinguishes from sibling tools by emphasizing 'single item' and 'primary key.'

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 includes explicit 'When to use' and 'When NOT to use' sections. It advises using prune_table for deleting all items and scanning first for non-key attributes, providing clear alternatives and exclusions.

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