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

The description mentions 'Body discarded,' which is a behavioral trait, but no annotations exist to carry the burden of disclosure. It does not mention rate limits, authentication, error behavior, or the fact that most parameters are discarded after checks, even though that information is embedded in the schema but not in the description. The description is too thin to be transparent.

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 short (one sentence), which is concise, but it lacks structural depth. It front-loads the primary purpose but omits necessary context, making it efficient yet insufficiently informative.

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?

With 9 optional parameters, no output schema, and no annotations, the description is woefully incomplete. It does not explain the tool's behavior with respect to the diverse parameters, when it should be used, or what the response format is. An agent cannot reliably invoke this tool correctly based on the description 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?

All 9 parameters have descriptions in the schema (100% coverage), so the schema provides meaning. The tool description adds no additional semantic value beyond what the schema already states, so the baseline score of 3 applies.

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 purpose: HTTP status for a public library docs URL, with body discarded. However, it does not clarify how the 9 unrelated parameters (city, feed, json, zone, query, etc.) fit this purpose, making the tool's actual scope ambiguous. It also does not differentiate itself from sibling tools like fetch-status or normalize-url.

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 guidance is provided on when to use this tool versus alternatives such as fetch-status, normalize-url, or web-fetch. The description gives no context about prerequisites, selection criteria, or exclusions, leaving the agent to guess.

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