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

The description explicitly mentions that the body is discarded, which is a useful behavioral detail. However, it doesn't mention any side effects, permissions, or rate limits. Since no annotations are provided, the description carries the full burden but only partially satisfies 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 itself is concise (one sentence). However, the overall structure is problematic: the tool exposes 9 optional parameters with nonsensical descriptions, making the input schema bloated and confusing, which undermines the conciseness of the description.

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 having 9 optional parameters and no output schema, the description is incomplete. It fails to explain how the parameters interact, which ones are mutually exclusive, or what the return value looks like beyond 'status and content type'. The mismatch between the parameters and the tool's purpose leaves significant gaps.

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?

Although the schema has 100% description coverage, the parameter descriptions are clearly generic placeholders (e.g., 'Git ref name; discarded after the shape check' for 'ref') that have no relation to fetching a URL. They mislead rather than clarify, and the tool description only mentions 'url' as relevant, leaving the other eight parameters unexplained and seemingly irrelevant.

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 the tool returns HTTP status and content type for a public URL, which is a clear verb and resource. However, it doesn't distinguish this from sibling tools like 'fetch-status' or 'browser-url-ok', so the uniqueness is not established.

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 provides no guidance on when to use this tool instead of alternatives. No conditions or scenarios are mentioned, leaving the agent to guess which of the many similar tools to pick.

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