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

With no annotations, the description carries the full behavioral burden and does well: it discloses irreversibility ('cannot be undone'), a cascade side effect ('Linked transaction associations are also removed'), and the required auth scope ('finance:delete scope'). It stops short of clarifying whether linked transactions themselves are deleted or merely unlinked, so 'associations' remains ambiguous.

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?

Three short sentences, front-loaded with the action and its permanence, then the cascade effect, then the permission requirement. Every sentence earns its place with no filler.

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 one-parameter destructive tool with no annotations and no output schema, the description supplies the key context an agent needs before invoking: irreversibility, cascading deletion, and required scope. The only real gap is the ambiguity around what happens to the linked transactions themselves.

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?

There is a single parameter with 100% schema description coverage ('UUID of the subscription to delete'), so the schema already carries the semantics. The description adds no format or sourcing detail (e.g., where to obtain the UUID), so the baseline of 3 applies.

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 first sentence gives a specific verb ('Permanently delete') and resource ('a subscription or recurring bill'), immediately distinguishing it from neighboring delete_* tools that target other resources. An agent can select this tool without opening the schema.

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 word 'Permanently' implicitly contrasts with the sibling toggle_subscription_active, but the description never names an alternative or states when deletion is preferable to deactivation/archiving. Usage is only implied.

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