vast42_delete_ad

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

With no annotations provided, the description carries the full burden. It states the delete action but does not disclose whether deletion is permanent, requires special permissions, or affects related objects. No warnings or side effects are mentioned.

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 conveys the essential operation with no superfluous words. It is appropriately concise for a simple delete 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?

The tool is simple (one parameter, no nested objects, no output schema). However, the description does not mention the success response, whether the operation is reversible, or any prerequisites. The lack of annotations and output schema leaves some behavioral gaps, but the minimal resource-destructive nature makes this borderline adequate.

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 input schema covers the single parameter 'id' with the description 'VAST 4.2 ad item ID' (100% coverage). The tool description adds no extra parameter details, but the schema already provides sufficient meaning for the required id.

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 VAST 4.2 ad item' uses a specific verb ('Delete') and resource ('VAST 4.2 ad item'), clearly distinguishing it from sibling tools like vast42_create_ad, vast42_update_ad, and vast42_list_ads.

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 on when to use this tool versus alternatives (e.g., vast_delete_ad_item or other vast42_delete_* tools). The name implies VAST 4.2 scope, but the description does not explicitly state preferred contexts or prerequisites.

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