delete_scene

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

Annotations already disclose destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations: that deleting a scene also deletes its models, and that deleting 'default' resets it to empty rather than destroying it.

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 short sentences, front-loading the core deletion behavior and immediately providing the special-case semantics. Every word earns its place.

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 one-parameter tool with clear annotations, the description is mostly sufficient. The main gap is the lack of an explicit schema description for scene_id to confirm what value it takes; because schema coverage is 0%, the description should have stated that scene_id identifies an existing scene, not just handled the 'default' special case.

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 single parameter scene_id is entirely undocumented. The description partially compensates by mentioning the 'default' special value, but it does not explicitly explain that scene_id identifies an existing scene or what other values are valid.

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?

Description states 'Delete a scene and its models' with a specific verb and resource. It clearly identifies this as a deletion operation, which distinguishes it from most sibling tools, though it does not explicitly name alternatives like update_scene or list_scenes.

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 implies usage around deleting scenes and gives a special-case behavior for 'default', but it doesn't explicitly say when to use this versus alternatives or mention prerequisites like ownership or permissions. It provides some context but no explicit exclusions.

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