delete_tileset

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

With no annotations provided, the description must fully disclose behavior. It states 'Delete', implying destructive action, but fails to mention whether the deletion is permanent, reversible, or if it cascades to associated data like tiles.

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 extremely concise with two sentences: the first states the core action, the second provides the sibling alternative. No redundant information.

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 tool with one parameter and no output schema, the description provides the essential purpose and sibling differentiation. Lacks behavioral details but adequate for a straightforward operation.

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 100% (tileset_id described as 'Tileset ID'). The description adds no additional meaning beyond the schema, as it merely reiterates 'by ID'. Baseline score of 3 is appropriate.

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 specifies the action 'Delete', the resource 'top-down tileset', and the identifier 'by ID'. It distinguishes this tool from its sibling 'delete_tileset_sidescroller' by indicating top-down vs sidescroller.

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 explicitly directs users to use 'delete_tileset_sidescroller' for sidescroller tilesets, providing clear guidance on when to avoid this tool. However, it does not elaborate on prerequisites or other exclusion criteria.

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