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

The description discloses one behavioral aspect (body discarded) but omits others like network access, potential side effects, error conditions, or rate limits. With no annotations to supplement, the description carries most of the transparency burden and does not fully address it.

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 concise and to the point, using two short sentences. However, it lacks any structural breakdown or explicit guidance, making it slightly less effective than a fully structured description, though still efficient.

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?

Given the tool's complexity and the schema's many irrelevant parameters, the description does not provide enough context to call the tool correctly. It fails to explain which parameters are actually required, what the response contains, or how it differs from similar tools, leaving the agent without essential guidance.

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?

The schema contains nine parameters, most of which are irrelevant to an HTTP fetch (e.g., 'city', 'feed', 'zone'). Their descriptions are generic and misleading, such as 'discarded after the shape check', which contradicts the tool's stated purpose. The description text does not clarify that only 'url' is meaningful, so parameter semantics are severely deficient.

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 performs an HTTP fetch and returns status and content type while discarding the body. It is a specific verb+resource and distinguishes itself from siblings like normalize-url or fetch-status by focusing on the response metadata.

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 offers no guidance on when to use this tool versus alternatives such as fetch-status or browser-url-ok. There is no mention of conditions, limitations, or when not to use it.

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