switch_display

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

Without annotations, the description is responsible for disclosing behavior. It only states the action and an example, but does not mention effects on the session, safety (destructive or not), or any side effects. This is insufficient for a mutation-like tool.

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 extremely short (one sentence), but it omits critical information, making it under-specified rather than concise. Every sentence should add value; here it fails to provide sufficient context.

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 simplicity (no nested objects, no output schema), the description should be complete. It is not: missing parameter format, usage context, and behavioral details. The tool's job is clear but the description is incomplete.

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 description coverage is 0%, so the description must explain the parameter. It gives an example (':10') but does not describe the format, valid values, or how the 'display' string is interpreted. The agent lacks needed semantic detail.

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's action ('switch the display') and provides an example format (':10'), making the purpose easy to understand. However, the term 'session targets' could be more explicit, but it's still adequate.

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 given on when to use this tool versus the many sibling tools (e.g., mouse_move, scroll). The description does not mention prerequisites or conditions for usage, leaving the agent to infer context.

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