request

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

With no annotations, the description carries full burden and discloses key behavioral differences: node uses server-side fetch (no CORS/cookies), browser uses tab's fetch (with session). However, it does not mention side effects like potential state changes from POST/PUT requests or error behavior beyond schema fields.

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?

Two sentences with no waste. The first sentence states the core purpose, the second explains the critical destination distinction. Information is 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?

Given 8 parameters and no output schema or annotations, the description is minimal. It explains destinations but lacks context on sequence steps (saveAs), required connectionReason for browser, and overall how this tool fits into the sequence workflow. Moderate completeness.

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 88%, so baseline is 3. The description adds semantic context for the 'destination' parameter by clarifying the runtime environment, but other parameters (url, method, headers) are adequately described in the schema already.

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 it makes an HTTP request as a sequence step and explains two destinations. It uses specific verbs and resources, but does not explicitly differentiate from sibling tools like 'navigate' or 'network', which have distinct purposes.

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 gives guidance on when to use node vs browser destination, but lacks overall usage context (e.g., when to prefer this over 'navigate' for URL loading or 'network' for intercepting requests). No explicit 'when not to use' or alternatives are mentioned.

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