press_key

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

No annotations provided. The description is overly brief, omitting details such as whether the press is a single keydown/keyup or hold, or if it requires the element to be focused. Behavior beyond the basic action is undisclosed.

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 sentence with no waste. It is front-loaded and to the point.

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?

Despite being a simple tool with one parameter and no output schema, the description lacks context about return value, error conditions, and potential side effects. It does not compensate for missing annotations.

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 only parameter 'key' is described only as 'keyboard key', with no format details (e.g., character vs. key name) or examples. Schema has 0% coverage, and the description fails to add meaningful semantic context.

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 the verb 'press' and resource 'keyboard key against active element'. It distinguishes from sibling tools like 'click' (mouse) and 'type' (text entry), though it could be more precise about the nature of the key press.

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?

No guidance on when to use this tool versus alternatives like 'type' or 'click'. No prerequisites or context for active element focus are mentioned.

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