adb_screen_size

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

No annotations are provided, so the description carries the burden. It does disclose the unit (pixels), which is genuinely useful behavioral context, but it does not say the operation is read-only, whether it targets the default device or requires a serial, or what the returned value looks like structurally.

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 short sentence with no filler, and the key fact (pixels) comes first. It is lean to the point of being slightly under-specified, but nothing is wasted.

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?

This is a simple one-parameter read tool, so the bar for completeness is low, but with no output schema the description should state the return shape (e.g., width/height, or a 'WxH' string) since parsing the result is the entire point of calling it.

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 100% and the single 'device' parameter is fully documented in the schema, including the omit-for-default behavior. The description adds nothing beyond that, so the baseline of 3 applies.

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 fragment names the resource precisely (screen size in pixels) and hints at its role, but there is no verb — nothing states that this is a 'get'/'read' operation versus something that configures the size. It is distinguishable from siblings like adb_tap or adb_swipe, but only by topic, not by action.

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 clause 'so taps and swipes can be aimed' implies the when-to-use context: call this before issuing adb_tap or adb_swipe coordinates. However it never explicitly names those sibling tools or says anything about when not to call it, so the guidance is inferred rather than stated.

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