set_axis_align

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action without mentioning side effects, requirements (e.g., node must be an auto-layout frame), invalid input behavior, or whether the operation is reversible. This is a mutation tool with no safety hints.

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 11-word sentence that directly communicates the tool's purpose with zero fluff. It is well-structured and front-loaded with the key action and resource.

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 has no annotations or output schema, and while the schema covers parameters, the description lacks additional context such as preconditions, error behavior, or return value. For a mutation tool with no safety annotations, this is insufficient.

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 100% coverage with detailed descriptions for all three parameters, including enum meanings and the note about SPACE_BETWEEN ignoring itemSpacing. The description adds no additional parameter information beyond what the schema already offers, so the baseline of 3 applies.

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 it sets primary and counter axis alignment on an auto-layout frame, identifying a specific verb, resource, and scope. This distinguishes it from sibling tools like set_layout_mode and set_padding, which handle different layout properties.

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 by specifying the target as an auto-layout frame, providing some context. However, it does not explicitly state when to use this tool instead of alternatives, nor does it mention any prerequisites or exclusions beyond the auto-layout requirement.

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