Unsubscribe from character reports

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

Annotations already provide destructiveHint=true and readOnlyHint=false, so the description's 'Delete' aligns with them. The added 'locally persisted' context is valuable, but the description does not go deeper into effects like irreversibility, cascading deletions, or what happens if the subscription ID does not exist. It earns a pass but not more.

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 a single focused sentence with no filler. It starts with the action verb and clearly states the object and scope, making it easy to parse quickly.

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?

This is a simple one-parameter destructive tool with annotations covering mutation and no output schema. The description states that the subscription is locally persisted, which is relevant operational context. It could mention expected return or failure behavior, but for a straightforward delete operation it is sufficiently complete.

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 0%, so the description carries the burden of explaining parameters. It does not explain subscriptionID at all beyond what the property name and schema format already show. The single parameter is fairly self-evident, but the description adds no semantic value for it.

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 states a specific verb and object: 'Delete one locally persisted character report subscription.' This clearly identifies the action and resource, and differentiates it from sibling tools like subscribe_character and list_character_subscriptions. The 'locally persisted' qualifier adds useful scope.

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 implies its usage: call it to delete a single saved subscription. However, it does not explicitly state when to use it versus alternatives, such as checking existing subscriptions first or creating new ones with subscribe_character. The guidance is only implicit, not explicit.

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