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

With no annotations, the description alone must convey behavioral traits. It discloses that the body is discarded and implies public URLs need no auth, but it fails to mention error handling, output format, rate limits, or side effects. For a tool with 9 parameters, this is minimal disclosure.

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 a single clear sentence with no filler. The core result and key behavioral note (body discarded) are front-loaded. Every word earns its place.

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 9 parameters, no annotations, and no output schema, the description is severely incomplete. It does not explain how the parameters relate to the reported output, which parameter is the primary URL, what the response structure looks like, or any constraints beyond 'public URL'. An agent would struggle to know how to invoke this correctly.

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 coverage is 100%, and each parameter has a descriptive comment in the schema (e.g., 'Git ref name; discarded after the shape check'). The tool description adds no parameter-specific information beyond the schema, so it lands at the baseline for high 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 action ('HTTP status and content type') and resource ('for a public URL'), and adds that the body is discarded. It is specific and not a tautology. However, it does not differentiate from the many sibling tools like fetch-status or browser-url-ok, so it loses one point.

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 on when to use this tool versus alternatives. The description does not mention any conditions, prerequisites, or explicitly name sibling tools for comparison. An agent is left without context for choosing this over similar URL-checking tools.

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