ssm_delete_parameters

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 behavioral disclosure. It only states the action ('Delete') and the resource, but does not disclose whether the deletion is irreversible, what happens if some parameters do not exist, or any side effects. The destructive nature is implied by the verb but no further transparency is offered.

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 delivers the essential action and resource without any redundant words or filler. It is well-structured for a simple delete operation.

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 tool is simple with one parameter and no output schema, but the description lacks behavioral context such as whether deletion is permanent or how errors are handled. While the operation is clear, additional context about the effect of the deletion would improve completeness, especially given the absence of annotations.

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 description already provides full coverage for the single 'names' parameter, including the max of 10 items. The description adds no further parameter semantics, so the baseline of 3 applies since the schema does the heavy lifting.

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 action (delete), the resource (SSM Parameter Store parameters), and the scope (multiple). It also indicates the context (LocalStack). The word 'multiple' distinguishes it from the sibling tool 'ssm_delete_parameter', making the purpose unambiguous.

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 usage for deleting multiple parameters, and the sibling 'ssm_delete_parameter' covers single deletion, but it does not explicitly state when to use one over the other. No exclusions or alternatives are named, so the guidance is implied rather than explicitly stated.

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