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

Annotations are absent, so the description must bear the full burden of behavioral disclosure. It reveals only that 'Page content is not stored,' but fails to mention side effects, network behavior, failure modes, or how the HTTP status is acquired; the schema's nine parameters and inconsistent 'discarded after' hints increase the ambiguity.

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?

No more than two sentences: the core purpose is front-loaded, and the caveat about storing page content is important and succinct. Every word earns its place, with no filler or redundancy.

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?

For a parameter with 9 optional fields, no output schema, and no annotations, the two-sentence description is too sparse. It does not explain what the tool returns and whether the ancillary parameters are ignored, which would leave an agent uncertain in which parameters to provide and what the response means.

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%, which sets the baseline at 3. The tool description adds no extra meaning to the parameters, merely referring to 'a URL' without explaining the role of the other eight fields or clarifying that only one may be relevant; it does not compensate for the contradictory 'discarded' cues in the schema.

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?

States a specific verb and resource: 'Return host, scheme, and HTTP status for a URL.' This is clear and action-oriented. However, it does not explicitly differentiate itself from siblings like fetch-status or normalize-url, which can produce overlapping information, so it falls short of a 5.

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?

Provides no guidance on when to use this tool versus alternatives. It does not name sibling tools or give criteria such as 'use this when you need only the host/scheme/status and not raw content'; 'Page content is not stored' is a behavioral note, not a usage guideline.

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