unity_ui_resolve

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

With no annotations provided, the description carries the full burden. It only states one behavioral trait (no asset creation), but does not disclose other aspects such as whether the tool is read-only, requires permissions, or has side effects beyond the scope.

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, 12-word sentence that conveys the essential purpose without any unnecessary text. It is maximally concise.

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 simplicity and lack of output schema, the description does not specify the return value format or any prerequisites. It leaves the agent guessing what the 'prefab spec' looks like and whether the output is returned directly or stored.

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 coverage is 100% with good descriptions for both parameters. The description adds context by specifying that the recipe is an 'AGS recipe' and that the output is a 'Unity uGUI prefab spec', which enhances understanding beyond the schema alone.

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 verb 'Resolve' and the resource 'AGS recipe into a Unity uGUI prefab spec', adding the important scope 'without creating assets'. This distinguishes it from sibling tools like `unity_ui_generate` that likely create assets.

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 implies usage when a spec is needed without asset creation, but lacks explicit 'when to use' or 'when not to use' guidance, and does not mention alternative tools.

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