Press Key

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

Discloses key behavior: dispatches to focused element and returns page snapshot. Without annotations, the description carries full burden; it lacks explicit mention of side effects (e.g., deletion with Backspace) but the action is inherently clear. A higher score would require more detail on potential consequences.

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, front-loaded with main action. No redundant information, every word earns its place. Efficient and clear.

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 no output schema, the description covers return value (fresh page snapshot). With three parameters and no complex nested objects, all necessary context is present for correct 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 covers 100% of parameters with descriptions, but the description adds context by giving concrete examples of key usage (Enter, Escape) and noting dispatch to focused element. This enhances understanding beyond the schema alone.

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 the verb 'Press' and resource 'single keyboard key', with explicit differentiation from sibling tool 'type' (for text entry). The tool's functionality is unambiguously described.

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 explicit when-to-use scenarios (submitting with Enter, dismissing with Escape, keyboard navigation) and when-not-to-use (use type to enter text). Also mentions the return of a fresh page snapshot, aiding agent decision-making.

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