delete_mylist

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

Beyond the annotations (destructiveHint=true), the description explicitly says 'Permanently delete' and 'obtaining explicit approval', which discloses irreversibility and a required confirmation step. This adds meaningful behavioral context not present in the annotations.

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, concise sentence that conveys the action, permanence, and prerequisite. Every word contributes meaning, with no redundancy or filler.

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 delete operation with a small parameter set and clear annotations, the description covers the essential behavior. It lacks detail about output/return values, but the absence of an output schema lowers the bar. The mention of approval is crucial given the destructive nature, making the description 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?

With 0% schema description coverage, the description compensates by implying the need for a list identifier ('identifying it') and a confirmation ('obtaining explicit approval'), directly mapping to list_id and confirm. However, it does not mention the optional account_id parameter, leaving a gap in full parameter coverage.

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 uses a specific verb 'delete' with a clear resource 'DigiKey MyList', and the qualifier 'Permanently' clarifies scope. It is distinct from sibling tools like remove_mylist_part, which removes a part rather than the whole list.

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 this tool is for deleting an entire MyList, setting it apart from part-level operations. It also adds a prerequisite ('after identifying it and obtaining explicit approval'), providing clear context on when to use it. However, it does not explicitly name alternatives or state when not to use it.

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