http_get

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

Annotations already signal read-only, idempotent, non-destructive behavior, so the description adds valuable context on top: automatic JSON parsing, redirect-following with SSRF re-validation on every hop, and refusal of private/loopback/link-local addresses unless both operator-level and per-call opt-ins are set. This discloses non-obvious security and parsing behavior beyond what annotations or schema convey.

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?

Three sentences deliver the core action, return payload, parsing behavior, redirect policy, and SSRF restrictions with zero filler. The most important operational facts are front-loaded before the safety caveat, making it easy for an agent to quickly decide and invoke.

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 having 11 parameters and no output schema, the description covers the returned shape, JSON parsing, redirect handling, and SSRF constraints, while the schema documents every parameter. The agent has enough to invoke the tool correctly and interpret its response; there are no material gaps requiring additional inference.

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%, and every parameter including url, retries, timeout_ms, max_bytes, basic_auth, bearer_token, and allow_private_hosts already has a meaningful schema description. The description adds only a brief echo of the allow_private_hosts SSRF nuance, so the baseline of 3 is appropriate; it neither hurts nor substantially compensates for schema documentation.

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?

States a specific verb and resource ('Perform an HTTP GET') and adds the return shape ('Returns status, headers, and body'), which makes the tool immediately identifiable among siblings like http_post, http_head, and fetch_html_to_markdown. The description goes beyond the tool name by specifying response contents and JSON parsing behavior.

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 given about when to prefer http_get over the many sibling tools, such as fetch_reader or fetch_html_to_markdown, or when it should be avoided. The description implies use for raw HTTP GET retrieval, but it never states exclusions or alternatives, leaving the agent to infer selection from the name alone.

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