Toggle on-device input visualization

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

Annotations already show idempotentHint=true and destructiveHint=false. The description adds critical behavioral info: persistence until reboot and the visual effects (markers, debug strip). No contradictions.

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 sentences, front-loaded with the main action, no fluff. Every sentence adds value: what it does, why useful, and when to use/disable.

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 (2 boolean params, no output schema), the description covers the core behavior, persistence, and usage recommendation comprehensively. No gaps for agent decision-making.

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?

Both parameters have schema descriptions, but the tool description adds value by explaining the effect of enabling (visible markers, live coords) and the persistent nature. For a 2-param tool with 100% schema coverage, this adds meaningful context.

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 that the tool toggles 'Show touches' and 'Pointer location' developer options, specifying the exact verb and resource. It distinguishes from sibling input tools by focusing on visualization, not the inputs themselves.

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 recommends enabling at the start of a driving session and disabling when done, providing clear context for usage. Missing explicit when-not-to-use or alternatives, but the recommendation implies a natural lifecycle.

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