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

It discloses that page content is not stored, but does not mention that it will likely make a network request, what side effects may occur, or how it handles invalid URLs or other parameters. With no annotations, this leaves important behavior undisclosed.

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 extremely concise and front-loaded: one sentence states the core action and result, and a second sentence provides a key non-behavior. No wasted words.

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?

Despite extreme conciseness, the tool is under-specified for its schema: it has nine optional parameters with no indication of expected combinations, no output format, and no error cases. The description alone is not enough to use it 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?

The schema descriptions are contradictory to the tool description (e.g., 'Git ref name', 'City name', 'JSON text') and the tool description does not explain which parameters are relevant or how they map to the promised URL result. This is actively misleading.

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?

Description clearly states the tool returns host, scheme, and HTTP status for a URL and adds that page content is not stored. This is a specific verb and resource, but the schema includes nine unrelated parameters, which muddies the actual purpose.

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 guidance on when to use this tool versus siblings like normalize-url, fetch-status, or web-fetch. The only hint is that page content is not stored, which implies it should not be used when full content is needed, but alternatives are never named.

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