cocos_add_scroll_view

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions attaching a scroll view but fails to explain whether this is a mutation operation, what permissions are needed, how it affects existing nodes, or any side effects like performance impacts. This leaves significant gaps in understanding the tool's behavior.

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 a single, efficient sentence that gets straight to the point without unnecessary words. It is front-loaded with the main action, though it could be slightly more informative given the tool's complexity.

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 (9 parameters, no annotations, but with an output schema), the description is inadequate. It fails to explain the tool's purpose in depth, parameter usage, or behavioral context, making it incomplete for effective agent use despite the presence of an output schema.

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 description only mentions content_id, ignoring the other 8 parameters (e.g., scene_path, node_id, horizontal, vertical, inertia). With 0% schema description coverage, the description does not compensate by explaining parameter meanings, purposes, or interactions, leaving most parameters undocumented.

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 the tool attaches a cc.ScrollView component and mentions content_id points to the scrollable content node, which clarifies the verb and resource. However, it does not differentiate from sibling tools like cocos_add_page_view or cocos_add_scroll_bar, which also handle scrolling UI elements, making the purpose somewhat vague in context.

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 provided on when to use this tool versus alternatives such as cocos_add_page_view or cocos_add_scroll_bar. The description lacks context about prerequisites, typical use cases, or exclusions, leaving the agent without clear usage direction.

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