Call a real API endpoint

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

With no annotations, the description carries the full transparency burden. It does disclose two important traits: the call is real/actual and the response is not validated. However, it does not mention that this can trigger mutating side effects (e.g. DELETE or POST), whether auth is needed or applied automatically, what happens on network errors or non-2xx statuses, or whether an API spec must be loaded first. For a tool that makes real network calls, these are material gaps.

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 two focused sentences with no filler. The primary behavior and return payload are front-loaded, and the key distinction from test_endpoint is given immediately afterward. Every sentence earns its place.

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 the tool's complexity — 9 parameters, a nested auth object, no output schema, and no annotations — this description is too thin. It covers the basic response characteristics and one sibling distinction, but leaves the agent without guidance on constructing path/openAPI requests, handling auth, avoiding accidental destructive calls, or interpreting failures. The schema partially fills some gaps, but the overall contextual picture is incomplete.

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 only 56%, and the description adds no parameter-level meaning. It does not explain how to supply pathParams versus queryParams, how the auth object works, what body should contain, or how headers are applied. The missing details for body, headers, pathParams, and queryParams are not compensated by the description.

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 states the exact action ('Make an actual HTTP call') and the exact resource ('a documented endpoint'), and explicitly lists the return values: real status, headers, and body. It distinguishes itself from the sibling test_endpoint by stating it does not validate responses, so an agent can tell them apart immediately.

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?

It names the direct alternative, test_endpoint, and gives the condition: use test_endpoint when schema validation is also desired. This is an explicit when-not/alternative instruction. Other siblings serve clearly different purposes such as loading specs or running test suites, so the key routing decision is covered.

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