sns_delete_topic

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

There are no annotations, and the description only says 'Delete an SNS topic' without disclosing important behaviors such as cascading deletion of subscriptions, idempotency, or failure modes for non-existent topics. This is a destructive operation, and the description fails to warn about side effects.

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, focused sentence that is perfectly concise and front-loaded. There is no redundancy or wasted wording, making it easy to parse quickly.

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 one-parameter delete, the description is minimally acceptable but lacks critical context such as the effect on associated subscriptions, whether deletion is idempotent, or the expected return value. Without annotations or an output schema, the description should provide more details to fully prepare the agent.

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 fully documents the only parameter (topicArn) with a description 'Topic ARN', so the description adds no additional semantic meaning. The baseline of 3 applies because schema coverage is 100%, and the description does nothing to enhance parameter understanding.

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 action ('Delete') and the resource ('SNS topic') with a specific scope ('LocalStack'), making it easy to understand what the tool does. It does not explicitly distinguish from sibling tools like sns_unsubscribe, but the resource name is 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?

No guidance is provided about when to use this tool versus alternatives (e.g., sns_unsubscribe for subscriptions or sqs_delete_queue for queues). It does not mention prerequisites or exclusions, so the agent gets no direction beyond the literal action.

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