delete_listing

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

The description discloses the destructive and irreversible nature of the operation. While no annotations exist, the description effectively communicates that the action is permanent. However, it lacks details on permissions, cascading effects (e.g., on associated images or files), or any confirmatory steps.

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 extremely concise, consisting of two short sentences. The first sentence clearly states the action and resource, and the second emphasizes irreversibility. No unnecessary words or repetition.

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 one parameter and no output schema, the description covers the key behavioral aspect (permanence). However, it does not mention preconditions (e.g., listing must be in a certain state) or what happens to associated data (files, images, orders). Sibling tools like delete_listing_file suggest there are related resources, but the tool description does not clarify if they are also affected.

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 already describes the single parameter 'listing_id' with a clear description. The tool description adds no additional semantic meaning beyond what is in the schema. Schema coverage is 100%, so a 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 clearly states the action ('Permanently delete') and resource ('a listing'). It is distinguished from sibling tools like create_listing, update_listing, etc., by focusing on deletion. The addition of 'This cannot be undone' reinforces the finality.

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 does not provide explicit guidance on when to use this tool versus alternatives. It is implied that one should use it to delete a listing, but there is no mention of preconditions, alternatives (e.g., soft delete if available), or when not to use it. Given the many sibling tools, more context would help.

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