set_layout_sizing

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

No annotations are provided, so the description must carry the full burden. It only says 'Set...sizing modes' and does not disclose any side effects, prerequisites beyond the auto-layout frame mention, or failure behavior. For a mutation tool with no annotation coverage, this is a significant gap.

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 sentence that front-loads the action and object, with no redundant or filler text. It is highly concise and effective.

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?

The tool modifies design state (mutation) with no annotations or output schema, yet the description provides only the bare action. It omits important context like the meaning of HUG/FILL, edge cases, or what happens if the node is not an auto-layout frame. This sparse coverage makes the tool underspecified for correct invocation in complex scenarios.

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 input schema provides comprehensive descriptions for all three parameters, including enum value constraints, so the description need not explain them. The description adds no additional parameter-level meaning, so it rests at the baseline 3.

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 tool sets both horizontal and vertical sizing modes on an auto-layout frame, identifying the specific resource and action. It distinguishes from siblings like set_layout_mode which controls layout direction, making the purpose unambiguous.

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 identifies the target context (auto-layout frame) which gives clear context for when to use this tool. However, it does not explicitly name alternatives or exclusions, so it earns a 4 rather than a 5.

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