hide_keyboard

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

Adds context beyond annotations: mobile-only, no-op behavior. Annotations already indicate idempotent and non-destructive; description aligns and adds usage nuance.

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?

Three concise sentences, front-loaded with main action, no unnecessary words.

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?

Adequate for a simple, no-op tool with no output schema. Specifies platform and usage timing, but could be more precise (e.g., platform list).

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?

No parameters, so description adds no param details. With 100% schema coverage and zero params, baseline is 4.

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 action (dismisses keyboard), resource (on-screen keyboard), and scope (mobile-only, no-op if hidden). Distinguishes itself from sibling tools as a unique utility.

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?

Explicitly recommends when to call ('after text entry when the keyboard obscures elements') and notes platform limitation. Lacks explicit exclusions or alternatives.

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