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

No annotations are provided, so the description carries the full burden. It discloses 'Body discarded,' which is a useful behavioral detail, but it fails to mention that many parameters are 'discarded after the check' (as in the schema) or that the tool appears to validate multiple types of inputs. It also omits error handling, rate limits, or auth. The description is minimally transparent but incomplete for a tool with such a broad schema.

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 one-sentence description is concise, but it under-specifies a tool with nine heterogeneous parameters. The 'Body discarded' clause is a useful detail, but the description lacks any mention of the non-URL capabilities implied by the schema. It is not efficiently structured for an agent to understand the full scope.

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 complexity of the schema (9 parameters, no required fields, no output schema, no annotations), the description is severely incomplete. It ignores the non-URL parameters (city, json, timezone, etc.) and does not explain what happens when those are supplied. An agent cannot determine correct usage across all input types from the text alone.

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 each parameter has a clear description in the schema. The description itself adds no parameter meaning beyond what the schema provides. According to the rubric, the baseline is 3 when schema coverage is high, which is the case here.

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 states a specific verb ('status and content type') and resource ('public URL'), and adds the 'Body discarded' detail. However, it does not differentiate from siblings like fetch-status or normalize-url, and the schema suggests the tool handles many non-URL inputs (city, json, timezone, etc.), which the description omits entirely. This creates ambiguity about the tool's actual scope.

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 explicit when-to-use or when-not-to-use guidance is provided. The description only implies use for public URLs, but with 27 siblings (e.g., browser-url-ok, fetch-status, normalize-url), there is no mention of alternatives or conditions. This leaves the agent to infer usage from the name and description alone.

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