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

With no annotations, the description carries the full burden of behavioral disclosure. It only states that the body is discarded, implying a non-content return. It does not disclose whether the tool makes network requests, follows redirects, has timeout behavior, or requires any permissions. It also does not mention the exact return format (only 'HTTP status' is implied). This is minimal and leaves critical behavior undisclosed for a network tool.

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 a single short sentence, which is concise but severely under-specified for a tool with 9 parameters and many siblings. The main verb is present, but the lack of detail makes it ineffective. It is not appropriately sized for the complexity; brevity here sacrifices necessary information.

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 tool with 9 parameters, no output schema, and no annotations, the description is grossly incomplete. It does not explain the return value beyond 'HTTP status', does not mention any error cases, does not clarify which parameter is the primary input, and provides no examples or edge-case handling. An agent would struggle to call this tool correctly.

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 coverage is 100% and the schema provides descriptions for all 9 parameters, so the baseline is 3. However, the description adds no parameter-specific meaning and, more critically, it conflicts with the parameter set: parameters like 'city', 'feed', 'zone', and 'query' have no apparent relation to the stated HTTP-status purpose. This inconsistency makes it harder, not easier, for an agent to determine which parameters are relevant, dropping the score below baseline.

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 verb and resource ('HTTP status for a public library docs URL') but is ambiguous: 'public library docs URL' is not a standard category, and the tool name 'lib-docs-hint' suggests it might be for hinting rather than a direct fetch. It does not differentiate from siblings like fetch-status or browser-url-ok, which also check HTTP status. The broad parameter set (city, feed, zone, query) further obscures the actual purpose.

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 vs alternatives. Siblings like fetch-status, normalize-url, and browser-url-ok perform similar checks, but the description does not mention any selection criteria, exclusions, or alternative tools. An agent has no way to know if this is the right tool for a given task.

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