netintel_web_fetch

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

No annotations are provided, so the description carries the full disclosure burden. It usefully reveals the egress model (server-side, apparently keyless) and the response convention (JSON auto-parsed, otherwise text), but says nothing about truncation, size caps tied to max_bytes, redirect handling, or error behavior on unreachable URLs.

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 content is dense and front-loaded, with the return format stated first and the sibling differentiation second. However, the text is visibly truncated mid-sentence ('No API key…'), which leaves the definition structurally incomplete rather than concise.

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?

With no annotations, no output schema, and 0% schema description coverage, the description is the only source of behavioral information and it falls short. It leaves 'max_bytes' unexplained, the truncation/error semantics undefined, and the trailing clause cut off, so an agent cannot predict what it gets back for large or failing fetches.

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 0% and neither parameter is documented in the schema. The description implies 'url' means any full URL but says nothing about format (scheme required? query strings? auth in URL?), and 'max_bytes' — the one parameter an agent could easily misuse — is never mentioned or explained as a truncation limit.

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 ('Fetch any URL'), the exact return shape ('raw body back — JSON parsed, everything else as text'), and the execution context ('safe server-side egress'). It also explicitly distinguishes itself from the /web/extract sibling whose markdown conversion it exists to bypass, so an agent can route between them without opening either schema.

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?

Gives a clear use case with concrete examples: data APIs (ArcGIS, government/open-data portals, blob storage) where markdown conversion mangles payloads. It does not state when *not* to use it (e.g., HTML pages better served by extract/markdown) nor mention rate limits or auth prerequisites, so it is contextual rather than exhaustive.

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