delete_list

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It clearly indicates this is a destructive operation ('Deletes'), which is critical information. However, it lacks details on permissions required, whether deletion is reversible, error handling (e.g., what happens if the list doesn't exist), or confirmation prompts. The memory-freeing note adds some context but doesn't fully cover behavioral traits.

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 appropriately sized and front-loaded, with the core purpose stated first ('Deletes an existing list by its ID.'), followed by a structured 'WHEN TO USE' section. Every sentence earns its place by providing essential guidance without unnecessary details, making it highly efficient and easy to scan.

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?

Given the tool's complexity (a destructive operation with no annotations and no output schema), the description is fairly complete. It covers the purpose, usage guidelines, and implies behavioral traits (destructive). However, it lacks details on return values, error cases, or side effects, which would be beneficial for a deletion tool. The high schema coverage helps compensate, but some gaps remain.

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 input schema has 100% description coverage, with the 'list_id' parameter well-documented as 'The list ID returned by create_list.' The description doesn't add any additional parameter semantics beyond what the schema provides, but with high schema coverage, the baseline is 3. The description's clarity about deletion purpose slightly enhances understanding, warranting a score of 4.

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 specific action ('Deletes') and resource ('an existing list by its ID'), making the purpose unambiguous. It distinguishes itself from siblings like 'create_list', 'get_list', and 'update_list' by focusing on deletion rather than creation, retrieval, or modification.

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 'WHEN TO USE' section explicitly provides guidance on when to use this tool ('To clean up lists that are no longer needed' and 'To free up memory after processing is complete'). This helps differentiate it from alternatives like 'update_list' for modifications or 'list_all_lists' for viewing, though it doesn't explicitly name those alternatives.

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