Delete Sharelist

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

Annotations already declare destructiveHint=true and idempotentHint=true, covering the mutation and repeatability profile. The description adds the ownership constraint and states that it returns the upstream API response on success. It does not contradict annotations. It adds context beyond annotations, though it does not elaborate on error behavior or response structure.

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?

A single sentence that front-loads the action, then adds the ownership restriction and return behavior. Zero waste, every clause adds value. Excellent conciseness.

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 delete operation with one required parameter, the description covers the action, scope restriction, and return value. The destructive and idempotent hints are in annotations. It does not mention authentication or error handling, but these are not essential given the tool's simplicity and annotation coverage. Slightly more could be added, but it is adequately 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 coverage is 100% with descriptions for both id and _jq. The description does not add meaning beyond the schema; it simply refers to 'by id' which is already documented. Baseline of 3 is appropriate since the schema carries the parameter documentation.

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 states a specific verb+resource: 'Delete a community sharelist by id.' It also adds a scope restriction (own lists only) that distinguishes it from other sharelist operations like sharelist_remove (likely removing a symbol) and sharelist_sort. The purpose is 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?

Provides explicit context on when to use: 'own lists only; subscribed lists cannot be deleted.' This tells the agent the condition for valid usage, though it does not name an alternative tool for subscribed lists. It is clear enough to prevent misuse, but could be improved by explicitly referencing an alternative.

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