set_fixed_position

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

Description states the core effect but fails to disclose default behavior when position is not specified, whether it affects layer tree order, or any requirements for parent constraints. With no annotations, the description carries the full burden, and 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?

Single sentence, no wasted words, front-loaded with the most important information. Highly 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?

For a simple tool with two parameters and no output schema, the description covers the basic purpose and examples, but lacks details on defaults and behavioral constraints. Adequate but not 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?

Schema covers both parameters with descriptions, so baseline is 3. The description does not add any extra meaning beyond what's in the schema.

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?

Description clearly states it pins a layer to stay fixed during scroll with concrete examples (sticky nav, floating button). However, it does not differentiate from sibling tools like create_scroll_behavior or set_constraints, which may have overlapping functionality.

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?

Provides examples that imply usage (sticky nav, floating button), but gives no explicit guidance on when to use vs alternatives, nor any exclusions or prerequisites. Adequate for a simple tool but lacks depth.

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