focus

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

Annotations declare readOnlyHint=false with destructiveHint=false, so the agent knows this mutates non-destructively, but the description adds nothing about what state changes (UI focus/selection), whether pattern and instrument indices must already exist, or what happens when no parameter is supplied. No mention of preconditions such as the app being launched.

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?

A single compact sentence with the three modes front-loaded. The only waste is the vague opener 'Shows something in the app's window', which could be dropped without loss.

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?

With 0% schema description coverage, three parameters, no output schema and no annotation explaining effects, the description is too thin: an agent cannot confidently decide between passing 'pattern', 'instrument' or 'view', or know the effect of passing several.

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 coverage is 0%, so the description must carry the burden, yet it only loosely maps names to actions and explains nothing about index semantics for 'pattern'/'instrument', valid ranges, zero-based indexing, or whether the three parameters are mutually exclusive selectors.

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 names three concrete actions (select pattern, select instrument, switch view) that map directly to the parameters, so an agent can tell what the tool does. The opening phrase 'Shows something in the app's window' is vague, and nothing distinguishes this from siblings like screenshot_app or app_status.

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?

Usage is only implied: selecting a pattern or instrument, or switching views, is the condition for calling it. There is no statement about when not to use it, whether multiple params may be combined, or which sibling (screenshot_app, get_song) to prefer for inspection instead.

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