subscription_introductory_offers_delete_instance

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about irreversibility, cascade effects on the parent subscription, required permissions, or error behavior. The only behavioral signal, 'DELETE', is already implied by the tool name 'delete_instance'.

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 short but wastes its only content by repeating the identical path string twice in parentheses, adding no information the first occurrence did not already carry. It is under-specified rather than genuinely concise.

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 destructive delete endpoint with no annotations, no output schema, and no other context, the description provides nothing an agent needs: no confirmation of destructive semantics, no prerequisites, no return or status information. It is inadequate for the operation's risk profile.

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?

Schema description coverage is 100% and the single 'id' parameter is documented in the schema as 'the id of the requested resource'. Per the baseline for high coverage, the schema does the heavy lifting and the description contributes nothing additional, so a 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 only restates the tool name as a REST path plus HTTP verb: 'DELETE /v1/subscriptionIntroductoryOffers/{id}', duplicated in parentheses. It conveys the resource and operation type but adds no plain-language statement of what the operation accomplishes, and gives no differentiation from siblings such as subscriptions_introductory_offers_delete_to_many_relationship or subscription_introductory_offers_update_instance.

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?

There is no guidance on when to use this tool, no prerequisites, no mention of alternatives, and no conditions for selecting it over sibling endpoints. An agent receives zero routing information.

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