dynamodb_delete_table

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

No annotations are provided, so the description must carry the full burden of disclosing behavioral traits. It mentions 'from LocalStack' but does not disclose that deleting a table is irreversible, removes all items and indexes, or that the table must exist. This is a significant gap for a destructive 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 concise sentence that effectively communicates the tool's purpose without unnecessary words. While it could include more detail, it is not bloated or vague, and the structure is appropriate for this simple tool.

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 simple delete operation with no output schema, the description might seem adequate, but it omits important context such as side effects (deleting all data) and prerequisites (table existence). Given the simplicity, it is marginally complete but lacks the depth expected for a destructive action.

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 description coverage is 100%, with the only parameter 'tableName' described as 'Table name'. The description adds no additional meaning beyond the schema, but for a single, well-named parameter, the baseline of 3 is appropriate.

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 'Delete a DynamoDB table from LocalStack' clearly identifies the verb ('Delete'), the resource ('DynamoDB table'), and the environment ('LocalStack'). It distinguishes from sibling tools like dynamodb_delete_item, which deletes an item, not a table.

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?

Usage is implied by the name and description: use when you need to delete a DynamoDB table. However, there is no explicit guidance on when to use this vs alternatives (e.g., dynamodb_delete_item) or when not to use it. The context is clear but no exclusions or alternatives are stated.

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