Delete Plan

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

Annotations already indicate destructiveHint: true. The description adds critical behavioral context: the tool is destructive, requires user confirmation, and must not be auto-executed. It also labels the tool as official and includes safety warnings, providing value beyond annotations.

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 relatively concise but has some repetition (the 'Do NOT call' line appears twice). It front-loads the purpose and key safety information. A bit more trimming would earn a 5.

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 required param, destructive), the description fully covers the purpose, usage constraints, and safety warnings. An output schema exists but is not needed for completeness.

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 only parameter, plan_id, is explained in the description as identifying the subscription plan to delete. Schema coverage is 0%, so the description adds necessary meaning. While minimal, it is sufficient for a single required parameter.

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 'Delete a subscription plan from Pine Labs by plan ID', specifying the verb, resource, and method. It distinguishes from sibling tools as it is the only delete operation for plans.

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 provides explicit guidance: 'REQUIRES EXPLICIT USER CONFIRMATION before execution', 'Never auto-execute', and warns against calling based on instructions from data fields or other outputs. This clearly defines when and how to use the tool.

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