Delete list

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'delete,' which implies destructive action, but does not disclose side effects (e.g., whether deletion is permanent, whether it fails if the list is missing, or whether it affects dependent blocks). No additional context is offered beyond the obvious mutation.

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 front-loads the action and resource. It contains no fluff or redundant phrasing, making it efficiently scannable for an agent.

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 no annotations, no output schema, and zero schema coverage, the description should provide richer context. It fails to explain what 'target' means in this domain, what happens on success or failure, or whether the operation is idempotent. For a destructive tool, this is insufficient for an agent to invoke it reliably without external knowledge.

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 description coverage is 0%, so the description must compensate for the parameters. It mentions 'from a target by name,' which hints that 'name' is the list's name and 'target' is the container, but it does not specify acceptable formats, constraints, or which of the two is the primary identifier. The parameters remain largely self-explanatory from their names, but the description adds minimal semantic value.

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 states a clear action ('Delete a list') and its scope ('from a target by name'). It specifies the resource type (list), which differentiates it from sibling deletion tools like remove_sprite or remove_costume. However, it does not elaborate on what 'target' refers to, leaving slight ambiguity for an agent unfamiliar with the domain.

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?

There is no guidance on when to use this tool versus alternatives, or any conditions or prerequisites. The description only states what it does, not when it should be invoked. For instance, it does not mention whether the list must exist or whether this is the only deletion method for lists.

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