cocos_add_dragonbones

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

No annotations are provided, so the description carries full burden. It implies a mutation ('Attach') but doesn't disclose behavioral traits such as permissions required, whether it modifies existing components, error conditions, or what the output schema contains. The prerequisite hint is useful but insufficient 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 with two short sentences that are front-loaded and waste no words. Every part ('Attach dragonBones.ArmatureDisplay' and the prerequisite note) earns its place without redundancy.

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 complexity (8 parameters, mutation tool), lack of annotations, 0% schema coverage, and presence of an output schema, the description is incomplete. It doesn't explain parameter meanings, behavioral implications, or what the output contains, leaving significant gaps for an AI agent to understand and invoke the tool correctly.

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%, meaning none of the 8 parameters have descriptions in the schema. The tool description adds no information about what parameters like 'scene_path', 'node_id', or 'dragon_asset_uuid' mean or how to use them, failing to compensate for the lack of schema documentation.

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 ('Attach') and the resource ('dragonBones.ArmatureDisplay'), providing a specific purpose. It distinguishes from sibling 'cocos_add_dragonbones_data' by referencing it as a prerequisite, though it doesn't explicitly differentiate from other 'add' tools in the 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 provides explicit guidance to 'use cocos_add_dragonbones_data first', indicating a prerequisite and sequence. However, it doesn't specify when to use this tool versus alternatives like 'cocos_add_spine' or other animation-related siblings, nor does it mention when not to use it.

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