press_caps_lock

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

With no annotations, the description carries the full burden of disclosing behavior. It clearly states that the tool does not know or care about the pre-tap state, which is a crucial behavioral trait. It doesn't mention other potential constraints (e.g., machine must be running), but for a simple toggle this is sufficient.

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 two sentences, front-loaded with the main purpose, and every sentence earns its place. It is concise and well-structured without any redundant 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?

The tool is simple, the output schema covers returns, and the description provides the necessary behavioral details and alternative tool guidance. It is complete enough for an agent to select and invoke this tool 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?

The schema has 0% description coverage (no parameter descriptions), and the description does not mention session_id at all. The parameter name is self-explanatory, but the description adds no semantic value beyond what the schema already shows. For a low-coverage schema, the description should compensate, and it doesn't.

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 tool taps CAPS LOCK once to toggle the current state, using a specific verb and resource. It also distinguishes itself from the sibling tool set_caps_lock by calling out that it is a pure toggle, making it easy to differentiate.

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?

The description explicitly provides an alternative: use set_caps_lock(session_id, on) when a deterministic final state is needed. This gives clear guidance on when to use this tool vs. the alternative, and why.

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