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

With no annotations, the description must carry the full burden of behavioral disclosure. It only states 'Body discarded,' which is minimal. It does not clarify that a network request is made, any side effects, rate limits, or why many parameters exist. This is a significant gap for a tool that appears to perform network I/O.

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 terse (one sentence) but lacks structure. It does not front-load the essential scope or list the parameter semantics. While concise, it omits critical information, making it under-specified rather than efficiently structured.

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?

Given 9 parameters, no annotations, and no output schema, the description is woefully incomplete. It does not explain the tool's behavior with most parameters, nor what the expected output format is beyond 'HTTP status.' An agent cannot reliably invoke this tool correctly based on the provided information.

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 covers 100% of parameters with individual descriptions, so the baseline is 3. However, the tool description adds nothing to clarify the parameters and actually misleads by implying only a URL is relevant. The description fails to explain why parameters like city, zone, or query exist, adding confusion rather than semantic value.

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 it returns HTTP status for a 'public library docs URL' and notes body is discarded, but the input schema contains 9 unrelated parameters (city, feed, zone, etc.) that are not explained. This creates ambiguity about the tool's actual scope and fails to distinguish it from siblings like fetch-status or browser-url-ok.

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 about when to use this tool versus alternatives. The description does not mention any conditions, exclusions, or sibling tools, leaving the agent to guess based on the vague name.

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