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

The description discloses that the body and some titles are discarded, but it does not explain parameter precedence, redirect/follow behavior, error handling, or side effects. With no annotations, the description carries the full burden and is insufficient.

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 short and front-loaded with an apparent purpose, with no filler words. However, the brevity contributes to ambiguity and omits essential context.

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 heterogeneous optional parameters and no output schema, the description is far from complete. It does not explain the return value, which parameters are accepted or combined, or how this tool relates to sibling tools.

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?

Each parameter has an individual schema description, so schema coverage is 100%, but the tool description does not map parameters to its stated purpose. It is unclear whether url, host, path, or feed is the intended input, and unrelated parameters like city, zone, json, and query are not reconciled with the 'HTTP status' purpose.

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 says 'HTTP status for a public library docs URL' but the 9-parameter schema includes unrelated fields (city, zone, json, query) and multiple URL-like fields (url, host, path, feed). It does not clarify which resource is being checked or what 'docs hint' means relative to siblings like fetch-status.

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 given on when to use this tool instead of fetch-status, browser-url-ok, normalize-url, validate-json, or other sibling tools. There are no conditions, exclusions, or selection criteria.

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