scene-delete-tileset-from-editable-tilemap

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

Discloses that the tileset asset is not deleted and that tile IDs are updated across layers. Provides useful side effects beyond the input schema, compensating for lack of 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?

Two concise sentences that efficiently convey purpose and key behaviors. No superfluous content.

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?

Adequately covers the deletion operation, including what is not affected and side effects. Lacks details on return value or prerequisites, but acceptable for a tool of this complexity.

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?

Description adds minimal extra meaning beyond the input schema, which already covers all three parameters with detailed explanations. Baseline 3 due to high schema coverage (100%).

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?

Clearly states 'Delete a tileset from an editable tilemap.' which specifies the action and resource. Distinguishes from siblings like scene-add-tileset-to-editable-tilemap and scene-fill-editable-tilemap-layer-data.

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?

Implies usage when wanting to remove a tileset, but no explicit guidance on when not to use or alternatives. Context from sibling tools suggests inverse of adding a tileset, but lacks clear direction.

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