blender_scene_delete

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

Annotations already flag destructiveHint=true, so the description's 'Delete' is consistent. It adds the last-scene constraint but does not disclose error behavior if trying to delete the last scene, nor how results are returned beyond 'Deletion result'.

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 and a returns line. Every sentence adds necessary information; no wasted words.

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 tool with one parameter and an output schema, the description covers the purpose and one constraint, but lacks details on error handling, what deletion entails, and specifics of the return value. Adequate but not fully complete.

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 one parameter 'scene_name' is described both in schema and description. The description essentially repeats the schema's description, adding no new semantic meaning. With schema coverage effectively 100%, 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 states the tool deletes a scene, with the note about not deleting the last scene. It distinguishes from sibling tools like blender_scene_create or blender_scene_list.

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 includes a critical constraint (cannot delete last scene) but does not explicitly state when to use vs. alternatives or provide exclusions. Among siblings, there is no other scene deletion tool, so confusion is minimal.

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