tap_runtime

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

The description explains the behavioral traits: switching runtime, default headless, chrome for real browser. This adds context beyond annotations (which only indicate idempotency and non-destructiveness). No contradictions found.

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?

The description is extremely concise: two main sentences plus a brief clarifier. Every word earns its place, and the core action is front-loaded.

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?

For a single-parameter tool with no output schema, the description covers all necessary context: purpose, usage scenarios, and disambiguation from sibling tools. No gaps.

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 coverage is 100% with enum descriptions, but the description further elaborates on when to use each value, adding practical context beyond the schema's literal definitions.

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 switches browser runtime mid-session and explicitly distinguishes itself from 'tap mcp connect', which registers the server. It uses specific verbs and identifies the resource (browser runtime).

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?

The description provides explicit guidance on when to use 'chrome' (login sessions, write operations) and 'headless' (default, switch back). It also clarifies that it is unrelated to another tool, preventing confusion with siblings.

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