delete_interest

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

Describes that the interest and its subscriber associations are removed, and that an error is returned if the interest does not exist. Annotations already indicate destructive and idempotent behavior; the description adds practical context but does not fully explain idempotency implications.

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: first sentence defines purpose, then usage guidance, then Args list, Returns, and Example. Each part is concise and front-loaded with key information.

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 purpose, parameters, return format, and example. Missing a note about the 'account' parameter and could elaborate on error handling, but overall sufficient for a simple delete tool.

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 explains the meaning and source for three required parameters (list_id, category_id, interest_id), adding value beyond the schema. However, the optional 'account' parameter is not mentioned, leaving a gap.

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 it deletes a single interest option from a category, preserving others. It distinguishes from the sibling tool delete_interest_category, making the purpose specific and unambiguous.

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 tells when to use this tool ('remove one specific option') and when to use the alternative ('delete_interest_category instead'). Also provides guidance on how to obtain required IDs from other tools.

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