hold_key

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

The description only says 'Hold down' but does not clarify whether the key is automatically released after the duration, how chords are specified (e.g., separator), or any side effects. With no annotations, more detail is needed for safe usage.

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, front-loaded with key information. It is concise but could include more detail without becoming verbose.

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 2 required parameters, no output schema, and no annotations, the description is insufficient. It omits the required format for 'text', behavior after duration, and any constraints, making it incomplete for an agent to use correctly.

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 only 50% (only duration has a description). The description adds no meaning to the 'text' parameter (e.g., format for chords) beyond the schema. The tool description does not compensate for the missing schema descriptions.

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 'Hold a key (or chord) down for a duration in seconds' explicitly states the verb (hold), resource (key or chord), and duration, clearly distinguishing it from sibling tools like 'key' or 'type' which likely involve pressing and releasing or typing characters.

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 is provided on when to use hold_key versus alternatives such as 'key' or 'type'. The description does not indicate context, prerequisites, or exclusions.

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