delete_promotion

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

Despite no annotations, the description is highly transparent: discloses permanent deletion, irreversibility, impact on discount codes, and that historical orders are unaffected. Also provides API endpoint and return structure.

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 well-structured with sections (purpose, API, return, side effects) and is concise. Minor fluff like the exact API endpoint could be omitted, but overall efficient.

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?

Given the tool's simplicity (one param, no output schema), the description is complete: explains when to use, side effects, and return structure. No gaps for an AI agent to understand invocation.

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?

Only one parameter 'promotion_id' with schema description 'promotion ID'. Schema coverage is 100%, so baseline is 3. Description does not add additional semantic detail beyond what the schema provides.

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 tool permanently deletes a promotion, specifying the purpose (clear expired/test/incorrect activities). It distinguishes from sibling tools like create/update/list by focusing on deletion.

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 'usually used to clear expired, test, or incorrectly created activities' provides clear context for when to use. No explicit alternatives are mentioned, but the purpose is well-defined.

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