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

With no annotations, the description carries the full burden. It does disclose that the body is discarded, which is a behavioral detail. However, it says nothing about how the other parameters (city, feed, json, etc.) are handled, whether the tool makes network calls, or what the return value looks like. The disclosure is minimal and incomplete.

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) but lacks structure. It does not front-load the full scope; it only mentions one narrow use case. For a tool with 9 parameters, this is under-specification rather than conciseness. It could be structured to list the main function and then note that it handles multiple input types.

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 the tool has 9 parameters, no annotations, and no output schema, the description is grossly incomplete. An agent cannot infer what the tool does for parameters like city, feed, json, path, zone, or query. The description only covers the URL case, leaving the rest ambiguous. It fails to explain the tool's actual behavior or how to use it 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%, so the baseline is 3. The description adds nothing beyond the schema's per-parameter descriptions. It doesn't clarify how parameters interact or which are used for the stated purpose. Since the schema is self-sufficient, the description doesn't need to repeat it, but it also fails to add any semantic context.

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.' However, it is extremely narrow and does not reflect the schema's 9 parameters covering city, feed, json, path, zone, query, etc. This suggests the tool may have broader functionality or the description is misleading. It also fails to differentiate 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 given on when to use this tool versus the many similar siblings (fetch-status, browser-url-ok, playwright-url-ok, normalize-url). It doesn't state any conditions or exclusions, leaving the agent to guess the appropriate context.

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