pilot_press_key

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

Describes returns (confirmation) and errors ('Unknown key') with reference to Playwright docs. Since no annotations exist, this covers basic behavior well, though side effects (e.g., form submission) are implied but not explicit.

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?

Concise with clear sections (parameters, returns, errors). Every sentence adds value; appropriately structured.

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 a single parameter, no output schema, and no annotations, the description fully covers purpose, usage, parameters, returns, and errors without gaps.

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 100%, but description adds value by providing examples (e.g., 'Shift+Enter') and explaining error handling, going beyond 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?

The description clearly states it presses a keyboard key or combination, listing common use cases (Enter, Tab, Escape, etc.) and distinguishing from siblings like pilot_type and pilot_click.

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?

Explicit examples of when to use (submit form, move fields, close modal) but does not name alternatives; however, the sibling list provides context. Clear guidance.

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