Delete Sharelist

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

Description adds value beyond annotations by stating that the tool only works on own lists and returns the upstream API response. Annotations already indicate destructive and idempotent nature, so the description provides additional contextual constraints.

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?

Description is extremely concise (27 words), front-loaded with the action, and contains no unnecessary words. Every sentence earns its place.

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 simple one-parameter delete operation with annotations covering destructiveness, the description adequately covers purpose, ownership constraint, and response. It could mention error handling or permissions, but overall is complete enough for an agent.

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 coverage is 100%, so baseline is 3. The description does not enrich the parameter meaning beyond 'by id', and the schema already describes 'id' as 'Sharelist ID'. No additional semantic value is added.

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?

Description explicitly states the action (delete), the target (community sharelist by id), and includes constraints (own lists only) that distinguish it from sibling tools like sharelist_remove and sharelist_create.

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?

Description provides a clear usage constraint: only own lists can be deleted, subscribed lists cannot. This tells the agent when and when not to use the tool, though it does not explicitly mention alternative tools for other sharelist operations.

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