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

The description adds the context that the response is returned as text, which is useful. However, it does not disclose potential side effects, network access implications, or handling of methods/body. Annotations provide only openWorldHint, so the description carries a burden it only partially fulfills.

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 a single, well-structured sentence that front-loads the core action ('Forward an HTTP request') and states the return type. It is concise and contains no filler words.

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 good schema coverage, the description is incomplete for a proxy tool. It leaves unanswered questions: what does 'target URL path' mean exactly? How does the method parameter affect the request? Are there restrictions on target URLs? No output schema exists, so the description should clarify the response format beyond 'body as text', which it does not.

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 schema already documents all three parameters adequately. The description adds no further meaning beyond what the schema provides; in fact, it introduces slight confusion by calling the url parameter a 'path' when the schema describes it as a target URL with a default hostname.

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 forwards an HTTP request through the Ona Prox proxy and returns the response body as text. It distinguishes itself from sibling tools like check_host or get_file, though it uses the ambiguous phrase 'target URL path' when the actual parameter is a URL/hostname with a default value of i.pximg.net.

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 guidance is provided on when to use this tool versus alternatives. It does not mention any prerequisites, exclusions, or scenarios where another sibling tool (e.g., search_host) would be preferred. The description is purely functional and lacks decision-support information.

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