classic_mac_click

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

No annotations to compensate. Description only says 'click' without disclosing that button, clicks, or target parameters affect behavior. For a tool with multiple parameters, more detail is needed (e.g., click-and-release, double-click support).

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?

Two concise sentences with no redundant information. Front-loaded with the core action and coordinate explanation.

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?

No output schema, no annotations, and 5 parameters but description is minimal. Missing information about return values, prerequisites (target must be online), and coordination with other mouse tools.

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 covers all 5 parameters with descriptions (100% coverage). Description adds minimal value beyond stating coordinates are screen-relative. No elaboration on button or clicks beyond what schema provides.

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?

Description clearly states the action (click), resource (screen coordinates on Classic Mac target), and distinguishes from siblings like move or type. The verb+resource combination is specific.

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 on when to use this tool vs alternatives. With 21 sibling tools, explicit context (e.g., 'use this to perform a click instead of a move or key press') would help an agent decide.

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