test_api_endpoint

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

With no annotations, the description carries the full burden. It discloses that auth cookies are handled automatically, which is useful, but it omits side effects, response structure, error behavior, or whether cookies are modified. For a tool that sends HTTP requests, this is minimal transparency.

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: the first states the primary action, the second adds a key behavioral trait. Both earn their place with no fluff or repetition. 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?

Despite six parameters and no output schema, the description is only two sentences. It doesn't describe the captured response format, error handling, or how auth is handled beyond a vague note. The tool's behavior in edge cases or with different methods/headers is unaddressed, leaving significant gaps for an HTTP request tool.

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 description coverage is 100%, so the baseline is 3. The description adds 'handles auth cookies automatically' which relates to includeCredentials but doesn't explain parameter usage beyond the schema. It neither compensates nor detracts from the schema's clarity.

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 sends HTTP requests and captures responses, with an additional note about auth cookies. It distinguishes itself from sibling tools like extract_api_data by focusing on sending and capturing rather than extracting data from a page. However, it doesn't explicitly name alternatives, so it's not a 5.

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 mention of when to use this tool versus alternatives like add_custom_header_to_request or intercept_and_modify_traffic. The description implies testing API endpoints, but provides no exclusions, prerequisites, or context for choosing this tool over others.

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