delete_scene

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

Annotations are absent, so the description carries the full burden of behavioral disclosure. It only states '删除一个场景' and '免费', revealing no side effects, irreversibility, permissions, or impact on related resources. For a destructive mutation tool, this is a critical omission.

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 short and front-loaded with the core action. It is concise to a fault, but the dimension measures appropriate sizing not informativeness. The '免费' addition is questionable but does not bloat the entry significantly.

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?

The tool is simple with one parameter, but given no annotations, no output schema, and zero parameter documentation, the description leaves critical context missing. An agent cannot know whether deletion is permanent, whether it cascades to related assets, or what constitutes a valid scene_id. This is inadequate for a destructive 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 0%, and the description adds no meaning beyond the schema. The only parameter, scene_id, is left undocumented; the agent receives no guidance on what it represents, how to find it, or any format expectations. The description does nothing to compensate for the schema's lack of detail.

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 specific verb and resource: '删除一个场景' (delete a scene), which is clear and unambiguous. It doesn't explicitly distinguish from sibling delete tools, but the resource 'scene' is distinct enough that an agent can infer this is the deletion action for 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?

No guidance is given on when to use this tool versus alternatives. There is no mention of alternatives like update_scene for modifying instead of deleting, nor any conditions or prerequisites for calling delete_scene. The only extra information is '免费' (free), which is irrelevant to usage selection.

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