Swipe Screen

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, but the description adds no behavioral context beyond the basic action. It does not mention whether the swipe triggers scrolling, navigation, or any other side effect, nor does it clarify the openWorld hint. The description provides no value beyond what annotations already convey.

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 extremely short and free of unnecessary words, but it borders on under-specification. It lacks any contextual or behavioral guidance that would help an agent use the tool correctly, so the conciseness is not paired with sufficient content.

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 the tool's six parameters and no output schema, the description is too sparse to provide complete context. The schema covers parameter semantics, but the description does not explain the tool's role in a mobile interaction flow, what happens after a swipe, or when it should be preferred over other gestures. A fuller description would be more helpful.

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?

The schema has 100% description coverage for all six parameters, so the description does not need to explain parameters. It also does not add any semantic detail beyond the schema. Baseline 3 is appropriate because the schema fully documents each parameter.

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 states a specific verb and resource: a swipe on the screen. This clearly distinguishes it from sibling tools like click, double-tap, and long-press. However, it is minimal and essentially restates the title without adding any nuance about the gesture's effect.

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?

No guidance is provided on when to use this tool versus the many sibling gesture tools (e.g., click, double-tap, long-press). The description gives no context about suitable scenarios, prerequisites, or alternatives, leaving the agent to infer usage from the name and schema.

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