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

With no annotations, the description must disclose behavior fully. It mentions 'Body discarded', which indicates the response body is ignored, but does not clarify whether the operation is read-only, what HTTP statuses are returned, rate limits, or side effects. The description also omits how the unrelated parameters (city, zone, etc.) are handled, leaving behavioral expectations unclear.

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 brief—one sentence with no wasted words, but it is under-specified to the point of being unhelpful. It lacks structure and front-loads a narrow use case while ignoring the tool's actual parameter diversity. Conciseness should not sacrifice essential information; here it does.

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 optional parameters and no output schema, the description is grossly incomplete. It does not explain the purpose of the tool beyond a single narrow case, does not mention which parameters are relevant to which scenarios, and provides no information about return values or errors. An agent would be unable to correctly invoke this tool for most of its declared parameters.

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 description coverage is 100%, so each parameter has a basic description. The tool description adds no parameter-specific meaning, but it does not contradict the schema either. According to the baseline, a score of 3 is appropriate when the schema covers all parameters and the description does not add extra context. The mismatch between the description's narrow focus and the broad parameter list is not a parameter semantics issue per se, but it does not enhance understanding.

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 'HTTP status for a public library docs URL' which implies a narrow purpose, but the input schema lists 9 diverse parameters (city, zone, query, etc.) unrelated to library docs. This mismatch makes the actual purpose ambiguous and fails to distinguish it from siblings like 'fetch-status' or 'browser-url-ok'. It is not a tautology but is vague and misleading about scope.

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 its many siblings (e.g., 'fetch-status', 'normalize-url', 'domain-shape'). The description does not mention any exclusions, prerequisites, or contextual triggers. An agent cannot determine if this is the right tool for a given task based on the description alone.

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