fetch

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does reveal two non-obvious behaviors: robots.txt restrictions are not followed, and the response body is returned as text. However, it says nothing about error handling, authentication needs, rate limits, or consequences of bypassing robots.txt, so the behavioral picture is incomplete.

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 only two sentences long, with the most decision-relevant fact (robots.txt bypass) front-loaded. There is no filler, and every clause adds useful information about what the tool does or returns.

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?

For a 7-parameter network tool with no annotations and no output schema, the description provides the return type but omits broader usage context such as error behavior, handling of non-2xx responses, and when the robots.txt bypass is appropriate. The fully described schema makes the tool callable, but the description alone is not complete enough to fully guide an agent through edge cases.

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 seven parameters and their meanings. The description adds no additional parameter-level context, but that is acceptable given the full schema coverage.

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's action and resource: fetch content from a URL, with the notable qualifier that it ignores robots.txt restrictions. It also specifies the return format as the response body as text. However, there are no sibling tools to differentiate from, so it stops short of the top score that requires sibling differentiation.

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?

The description gives no explicit guidance on when to use this tool or what alternatives might exist. The robots.txt bypass implies a specific use case, but that is left for the agent to infer rather than stated directly.

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