tap_expand_tools

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

Annotations provide openWorldHint: true; description adds that after calling, server sends notifications/tools/list_changed and clients re-query tools, which is valuable beyond annotations.

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 moderately long but well-structured, front-loaded with purpose. Could be slightly more concise, but every sentence adds value.

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 no output schema, the description fully explains the tool's effect (exposes additional tools) and the client-side behavior (re-querying tools list). Complete for the complexity.

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?

Only one parameter (level) with enum values; description adds meaning by listing what each level exposes (creative, manual, and specific tool names like tap.click, tap.type), greatly enhancing the 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?

The description clearly states the tool expands the MCP tool set, specifies when to use it (default set insufficient), and gives concrete examples. It distinguishes from sibling tools like tap_list.

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 when to call (default Layer-1 set insufficient), provides examples (manual browser actions, write-tap ops, diagnostic probes), and explains levels and their subsumption.

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