subscription_offers_delete

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

With no annotations, the description must disclose behavioral traits. It merely states 'Delete' without explaining whether the operation is reversible, if it affects active subscriptions, or any side effects. This is insufficient for an agent to understand the tool's impact.

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 only two words, which is not concise but rather under-specified. Every sentence should add value, and this description provides minimal information.

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 no output schema and 4 required parameters, the description is critically incomplete. It does not explain return behavior, error conditions, or lifecycle implications. A delete tool needs far more context.

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 has 50% description coverage (only packageName and productId described). The tool's description adds no parameter information, failing to compensate for the missing basePlanId and offerId semantics. Baseline 3 is not met due to incomplete schema and no supplementary description.

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 an offer.' indicates the action but does not differentiate from siblings like subscription_offers_deactivate or batch delete operations. It is a tautology that restates the tool name without specifying what type of offer or the uniqueness of this 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?

No guidance is provided on when to use this tool versus alternatives such as deactivate or batch update. The description lacks context on prerequisites, consequences, or scenarios where delete is appropriate.

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