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

Discloses best-effort behavior and Accessibility permission requirement. Annotations have readOnlyHint=false, destructiveHint=false; description adds context without contradiction.

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?

Three sentences, no wasted words. First sentence states main action, second explains limitations, third states permission. Front-loaded and efficient.

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?

Covers main action, limitations, fallback, and permissions. No output schema, but return values are implicit. Adequately complete for a click tool.

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 3 parameters are described in schema (100% coverage). Description adds no extra parameter details beyond schema, but overall context aids understanding. Baseline 3 is appropriate.

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 'Clicks a status-bar (menu bar extra / NSStatusItem) item and optionally follows a nested menu path', specifying verb and resource. It distinguishes from sibling ui_click by mentioning fallback to coordinate-based click.

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?

Explicitly states 'apps that render fully custom (non-AX) menus may not be reachable (fall back to ui_click at known coords)', providing when to use and alternative.

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