cocos_delete_node

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: it's a soft-delete (not permanent), involves disconnecting from parent and deactivating, and maintains stable indices. However, it lacks details on permissions, reversibility, or error conditions, which are important for a mutation tool.

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—two short sentences with zero wasted words. It front-loads the core action ('Soft-delete a node') and adds clarifying details efficiently. Every sentence earns its place by providing essential 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?

Given the tool's complexity (a mutation with 2 parameters), no annotations, and an output schema (which reduces need to describe returns), the description is moderately complete. It covers the core behavior but misses parameter explanations and usage context, leaving gaps for an agent to infer.

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 schema provides no parameter details. The description doesn't explain what 'scene_path' or 'node_id' represent, their formats, or constraints. It adds no semantic value beyond the schema's property names, but the baseline is 3 due to only 2 parameters.

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 action ('Soft-delete a node') and specifies what that entails ('disconnect from parent, deactivate'), distinguishing it from siblings like 'cocos_remove_post_build_patches' or 'cocos_set_node_active'. It explicitly defines the operation as a soft-delete, not a permanent removal.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, such as whether the node must exist or be active, or compare it to other deletion-related tools in the sibling list. Usage context is implied but not explicit.

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