Set device conditions (preset)

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

With no annotations, the description carries the full burden and does well: conditions report applied/skipped/failed, unsupported ones are skipped with a reason, and explicit fields override presets. It also flags the app_id requirement for the international preset, adding meaningful behavioral context.

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 long but densely informative, with a front-loaded core sentence followed by organized preset definitions. Each clause earns its place, though it could be slightly tighter.

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 9-parameter tool with nested objects and no output schema, the description covers the main usage modes, preset semantics, override behavior, and error/skip reporting. It stops short of explaining every parameter interaction or return format, but is largely complete for the tool's intended use.

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 only 44%, so description must compensate. It richly documents preset enum values and override behavior, and clarifies locale/app_id. However, explicit fields like network, location, appearance, font_scale, and orientation are not individually detailed in the description, leaning on self-explanatory schema names.

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 'Apply multiple device conditions in one call', identifying a specific action and resource. Preset definitions like 'screenshot' and 'accessibility' further distinguish it from individual set_* sibling tools.

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?

Explicitly says to use 'a named preset and/or explicit fields' and that 'explicit overrides the preset', giving clear usage direction. The 'edge-case states where bugs hide' provides context, though it doesn't explicitly name alternative tools.

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