deleteMembershipPlan

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

Adds context beyond annotations: permanent deletion, no undo, no soft-delete, records unrecoverable, and members become orphaned. Annotations already indicate destructive, but description enriches with specifics.

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?

Well-structured with clear sections (Use when, Required, See also, Destructive, Returns). Every sentence is purposeful and 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?

Covers prerequisites, consequences, return format, and links to related tool. No output schema but return is described. Complete for a delete operation.

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 (subscription_id) with 0% schema description coverage. Description mentions it is required but does not elaborate beyond that. For a simple ID parameter this is acceptable but minimal.

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?

Clearly states it permanently deletes a membership plan by ID. Distinguishes from sibling delete tools by specifying resource type, and from updateMembershipPlan as an alternative.

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?

Explicitly says when to use (retiring a plan with no members), warns about orphaned members and suggests migration via updateUser, and advises user confirmation before bulk use.

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