pointer

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

No annotations provided, so description carries full burden. It discloses coordinate system, action behaviors, 'then' chaining, and auth override. However, it lacks explicit information on error handling or side effects like destructive actions.

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?

Description is a single dense paragraph that front-loads the core concept. It covers actions and special parameters efficiently. Could be more structured (e.g., list actions), but remains clear and concise.

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?

Tool has 11 parameters and an output schema (not shown). Description covers key actions and special parameters well. However, it does not fully explain parameter combinations or error handling, leaving some gaps for complex use cases.

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 0%, but description explains parameters for each action (e.g., x,y for move, button for click). It adds meaning beyond schema titles, though scroll_dx is omitted. Overall, it compensates well for missing schema descriptions.

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 is for mouse operations in global coordinates, lists all actions (move, click, drag, scroll), and explains special parameters like 'then' and 'allow_auth'. It distinguishes itself from sibling tools like keyboard or desktop.

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 implies usage for mouse input and provides context like coordinate system and action options. It mentions 'allow_auth' for authentication dialogs but does not explicitly contrast with alternative tools or specify when not to use.

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