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

With no annotations, the description carries the full burden. It does disclose that page content is not stored, which is a useful side-effect guarantee, but it does not mention whether the tool performs network requests, whether it follows redirects, or what failure modes exist.

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 front-loaded with the core verb and outcome. It loses a point because the schema mismatch creates ambiguity that a slightly longer description could have resolved.

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?

The description is incomplete for a tool with four optional-looking parameters. It does not explain how url, host, json, and zone relate, whether they are mutually exclusive, or what output format to expect, especially since no output schema is provided.

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 tool description only concerns URLs, but the schema includes four parameters: url, host, json, and zone. The descriptions for host, json, and zone are unrelated to the stated purpose and appear to be from different tools, making the parameter semantics confusing and internally inconsistent.

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 returns host, scheme, and HTTP status for a URL, and it distinguishes itself by noting page content is not stored. However, it does not explicitly differentiate from sibling tools like normalize-url or status-catalog beyond this single caveat.

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 gives minimal guidance on when to use this tool versus alternatives. It only says page content is not stored, which hints at a citation use case, but it does not mention normalize-url, status-catalog, or other siblings, leaving the selection criteria vague.

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