gameobject-modify

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

No annotations are provided, so the description carries full burden. It states 'Modify' but does not disclose behavioral traits such as whether the operation is destructive, requires saving, or has side effects. No details on error handling or success indicators.

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 concise sentences that front-load the purpose and quickly provide a usage hint. No unnecessary words, and every sentence adds value.

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 no annotations and no output schema, the description is minimal. It explains the basic functionality and the length constraint but lacks behavioral context, error conditions, or return value information. Adequate for a simple tool but could be more complete.

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 schema covers both parameters with examples, but the description adds value by clarifying that the arrays must have the same length and mentioning 'SerializedMember objects', which maps to the 'gameObjectDiffs' parameter. This goes beyond the schema's basic type info.

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 ('Modify'), the target resource ('GameObject fields and properties'), and the context ('opened Prefab or in a Scene'). It also mentions the ability to modify multiple GameObjects at once. However, it does not differentiate from sibling tools like 'gameobject-component-modify' or 'object-modify', so it misses some specificity.

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 explicit guidance on when to use this tool versus alternatives. It only mentions the context of opened Prefab or Scene, but does not state when not to use it or what other tools are better suited for similar tasks.

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