delete_subscribe

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

With no annotations provided, the description carries the full burden. It discloses deletion behavior, supported ID types, and the conditional season parameter, but lacks details on return format, error handling, or side effects beyond a generic 'result information' note.

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 succinct and organized, front-loaded with the purpose, followed by a clear list of args and returns. Every sentence adds value, with no superfluous content.

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?

While parameter explanations are thorough, the return value description is vague ('result information') and there's no mention of potential errors or prerequisites. For a delete tool without annotations or output schema, this is a notable gap.

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 description fully explains all three parameters, including enum values, examples, and the conditional behavior of season, compensating for the 0% schema description coverage. It adds meaning beyond the schema's title and enum definitions.

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 the tool deletes a subscription and supports deletion by subscription ID or media ID (tmdb/douban). This distinguishes it from sibling tools like add_subscribe, update_subscribe, and get_subscribe, with a specific verb and resource.

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 usage for deleting subscriptions but provides no explicit guidance on when to use this tool versus alternatives like update_subscribe. It does give specific guidance on when the season parameter is applicable, which is a partial usage guideline.

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