Server Quality Checklist

Tool Scores

• http_requestA
  4.2/5.0
  Behavior4/5

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

  Beyond the annotations (readOnlyHint=false, openWorldHint=true), the description discloses that the agent selects method, URL, headers, query parameters and body, and that the response includes status, headers, content-type, and body. It also adds a non-obvious security behavior: header values of the form '${VAR}' are resolved from server environment variables without exposing the token to the agent. This is valuable contextual information beyond the structured schema.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a succinct three-sentence block. It front-loads the core action in the first sentence, then efficiently covers request components, response fields, and supported methods without redundancy or filler. Every sentence contributes information.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool's generic nature and eight parameters, the description plus rich schema details and output schema provide solid coverage. It mentions the response return fields (status, headers, content-type, body) and a key security nuance. Minor gaps like error handling or redirect behavior are already covered in the schema (follow_redirects). The overall package is sufficiently complete for an agent to invoke it correctly.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 100%, with each parameter already well-documented in the input schema (e.g., 'data' as raw text body alternative to json_body, 'params' as query string dict). The description's mention of the agent picking method, URL, headers, etc., is a high-level summary that adds no new semantic meaning over the schema, so the baseline score of 3 is appropriate.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description opens with 'Send an arbitrary HTTP request and return the response,' which is a specific verb+resource statement. It further clarifies the tool's scope by enumerating supported methods (GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS, TRACE) and explicitly labels itself as the 'single generic HTTP client tool,' making its purpose unmistakable.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description states this is the 'single generic HTTP client tool' and lists the components the agent controls (method, URL, headers, query parameters, body), giving clear context on when to use it. With no sibling tools provided, there is no explicit alternative, but the intended usage as the universal HTTP request tool is clear.

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