app_window

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

With no annotations provided, the description takes on full disclosure duty. It explains that 'set' uses coordinates while other actions ignore them, and that omitted axes are unchanged. This goes beyond the schema by describing runtime behavior and side effects (reporting size+position).

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 two sentences long, front-loaded with the essential action verbs, then efficiently details parameter behavior and a use case. Every sentence adds value without redundancy.

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 5 parameters, no output schema, and no annotations, the description covers all actions, parameter interaction, and a use case. It could optionally describe the return value format for the reported size+position, but the current description is adequate for tool selection and invocation.

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?

All 5 parameters are covered in the description. It clarifies that 'action' defaults to 'set', that for actions other than 'set' the coordinate parameters are ignored, and that omitted axes for 'set' are left unchanged. This adds rich semantics over the bare schema (which has 0% description coverage).

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 the tool resizes, moves, maximizes, minimizes, or fullscreens the app window and reports size+position. The verb 'Resize, move, etc.' and resource 'app window' are specific and distinct from sibling tools like app_click or app_screenshot.

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 provides a concrete use case: 'useful for consistent screenshots or checking responsive layout.' While it does not explicitly exclude alternatives, the context is clear and helpful for selecting this tool.

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