apk_preview_configure_display

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

Annotations already indicate this is a mutating operation (readOnlyHint=false) but not destructive. The description's 'Switch' is consistent but adds no behavioral detail beyond that, such as whether changes apply live, require a restart, reset when the session stops, or affect the running app.

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?

One short sentence with no filler, and the key settings are clearly front-loaded. It is appropriately sized for a configuration tool and avoids redundant restating of the schema.

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 four parameters, zero schema descriptions, and a mutating side effect, this is too thin. It omits prerequisites like an active session, the meaning/range of font_scale, and the implications of changing the profile or orientation. The presence of an output schema helps with return values, but not with correct invocation context.

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 needs to carry the semantic weight. It simply repeats the parameter names (profile, orientation, theme, font scale) without explaining what the enum values mean, what font_scale values are valid, or how profile choices differ. This adds little beyond what the input schema already shows.

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 uses a specific verb ('Switch') and identifies the resource ('emulator screen') along with the exact dimensions being configured: profile, orientation, theme, and font scale. It clearly distinguishes this tool from siblings like apk_preview_inspect_screen or apk_preview_interact, which are about reading or acting on the screen rather than configuring it.

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 gives no guidance on when to use this tool versus siblings. It does not mention that an active emulator session is required, does not describe sequencing relative to apk_preview_start_session or apk_preview_launch_app, and does not contrast with inspect_screen or interact.

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