Get or set caps lock

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

Without annotations, the description carries the transparency burden. It explicitly mentions that calling with no arguments only reports, implying that providing the 'enabled' parameter changes the state. It also notes the keyboard light effect, but does not mention potential side effects or permission requirements.

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 concise, comprising two short sentences that cover the core functionality and the optional argument behavior. No redundant words or filler.

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 the tool's simplicity, the description covers its purpose and usage with and without arguments. It does not specify the exact return format when reporting, but given the lack of an output schema and the straightforward nature, this is a minor gap.

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 single parameter 'enabled' is clearly described in both the schema and the description: omitting it reports, providing it sets the state. The parameter semantics are fully covered with no ambiguity.

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 reads or changes the caps lock state, including its keyboard light. It is specific to caps lock and distinct from sibling tools that manage other system settings.

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 provides a usage hint: 'Called with no arguments it only reports.' However, it does not explicitly explain when to use this tool versus alternatives, nor does it describe how to perform a set operation beyond the schema property.

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