wavexis_tap

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

Description only mentions return format (status 'ok'). Annotations flag non-readonly and non-idempotent, but description adds no behavioral context about side effects, prerequisites, or error conditions.

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?

Very brief (two sentences), no unnecessary words. Could include more detail without being verbose, but structure is clean.

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?

With 6 parameters and no output schema beyond a simple status, description fails to cover prerequisites (e.g., element visibility), error scenarios, or relationship to other actions. Incomplete for reliable agent usage.

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?

Description does not explain any parameters; merely says 'Tap parameters'. Schema has descriptions only for 'selector', but overall coverage is low. Description adds no value beyond schema.

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 'Tap an element (touch emulation click)', distinguishing it from siblings like click, hover, etc. Specific verb + resource.

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 tap versus alternatives (e.g., click, hover). Lacks context for selection among many sibling tools.

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