oc_normalize_action

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

Annotations already indicate read-only, non-destructive, idempotent. Description goes further with 'side-effect-free: it does not touch Chrome, CDP, tabs, DOM, cookies, storage, or files.' Lists exactly what is not affected, adding valuable behavioral context beyond annotations.

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 sentences: first sentence front-loads purpose and key qualifiers (validate, normalize, near-valid, without executing), second sentence emphasizes side-effect-free nature. No wasted words, all essential information.

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 output schema exists (not shown but indicated), description covers purpose, usage context, behavioral traits, and parameter semantics adequately. No missing critical information; the tool is well-described for agent usage.

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 descriptions for all 4 parameters. Description adds minimal extra value beyond schema; it restates that action is never executed, but schema already says 'Action is never executed.' Baseline 3 is appropriate.

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?

Clearly states 'Validate and normalize a near-valid browser/computer action payload without executing it.' Identifies the specific resource (action payload) and verb (validate and normalize). Differentiates from sibling execution tools by emphasizing non-execution, making its unique purpose obvious.

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?

Explicitly advises 'Use this before calling real action tools when a host model produced aliases such as left_click, hotkey, coordinate, or missing click button.' Provides clear context for use, though could strengthen with explicit when-not-to-use or alternative tool names.

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