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

With no annotations, the description must disclose behavior. It only says 'Body discarded,' which is a minor detail. It doesn't state that it makes network requests, returns only a status code, or what happens with each parameter. The description contradicts the schema's breadth, suggesting a single-use case while the schema implies multiple.

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 sentence, which is concise but under-specified for a 9-parameter tool. It lacks structure and front-loads a narrow use case, leaving out 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?

Given 9 optional parameters, no annotations, no output schema, and no usage guidance, the description is completely inadequate. An agent cannot determine what this tool does with different inputs, what it returns, or when to invoke it.

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 description adds no parameter meaning beyond the schema. While schema coverage is 100%, the description doesn't clarify how parameters like 'city' or 'query' are used. The single mention of 'library docs URL' conflicts with parameters that are not library-related.

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 (HTTP status) and resource (public library docs URL), but the schema accepts 9 unrelated parameter types (city, feed, json, path, zone, etc.) with no mention of library docs in most of them. This makes the stated purpose misleading and fails to distinguish 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 on when to use this tool versus any of the 26 siblings. No exclusions, no context, no mention of alternatives.

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