Touchpoint

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

With no annotations provided, the description carries the burden. It explains the 'raw' nature vs convenience functions and documents the prerequisite dependency on get_element. However, it lacks disclosure on side effects, error handling, or what constitutes a successful execution.

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?

Appropriately sized with front-loaded value: first sentence states purpose, second gives usage condition, third provides workflow prerequisites. Every sentence earns its place without repetition of structured data.

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 output schema exists, the description avoids unnecessary return value explanation. It sufficiently covers the complexity of raw accessibility actions by explaining the prerequisite workflow and providing concrete action name examples, though it could briefly mention invalid action handling.

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?

With 0% schema description coverage, the description fully compensates by documenting both parameters. While element_id is minimal ('The element ID'), action_name includes precise examples ('activate', 'expand or collapse', 'ShowMenu') that clarify the expected string format.

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 uses specific verb 'Perform' with resource 'raw accessibility action' and explicitly distinguishes from siblings by mentioning 'convenience functions (click, focus, etc.)', making the scope clear.

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?

Provides explicit when-to-use ('when the convenience functions...do not cover what you need'), names specific alternatives (click, focus), and gives clear prerequisite workflow ('Call get_element first...then pass the exact name here').

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