list-delete

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

With no annotations, the description must fully disclose behavior. It states the action (delete) but omits consequences such as irreversibility, cascading deletion of associated items (e.g., cards), or permission requirements. This lack of detail could lead to misuse.

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 very concise: one sentence plus a tag. It front-loads the primary action. However, it could be slightly more structured with a separate note about prerequisites or side effects while remaining concise.

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 with one parameter and no output schema, the description covers the basics. However, it lacks behavioral context (irreversibility, permissions) and any mention of return codes or confirmation. It is minimally adequate but not comprehensive.

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 0%, so the description must compensate. It adds that the identifier is a 'public ID', which is marginally helpful, but does not explain the format, constraints, or how to obtain it. For a single parameter, more detail is needed.

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 verb 'Deletes', the resource 'list', and the identifier 'by its public ID'. This unambiguously tells the agent what the tool does and distinguishes it from sibling tools like 'list-create' and 'list-update'.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., list-update to modify instead of delete). There is no mention of prerequisites, side effects, or scenarios where deletion is appropriate. The 'Tags: Lists' adds minimal context.

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