expand_settings

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

With no annotations, the description only mentions a prerequisite. It does not disclose other behaviors (e.g., toggling behavior, Android version requirements, or side effects) beyond the basic action.

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 a single, front-loaded sentence with no extraneous words. Every part (action and prerequisite) earns its place.

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?

For a simple tool with one optional parameter, the description is adequate but minimal. It could benefit from explaining the panel's purpose or result state, though sibling context somewhat compensates.

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 100% with 'Device serial number' for the only parameter. The tool description adds no further parameter meaning beyond what the schema already provides.

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 'Expand the quick settings panel', a specific verb and resource. It distinguishes from siblings like 'expand_notifications' and 'collapse_panels' by naming a different panel.

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 notes a prerequisite ('requires active scrcpy session') but provides no guidance on when to use vs. alternatives like swipe or tap, nor what happens if already expanded.

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