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

With no annotations provided, the description bears the full burden of behavioral disclosure. It only mentions that no browser is launched, but does not clarify what actions it actually performs (e.g., network request, syntax validation), side effects, permissions, or error behavior. This is a significant gap for a tool with zero annotation coverage.

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 concise sentence that states the core action and a key behavioral constraint. It is front-loaded and contains no fluff, though it could benefit from a bit more elaboration on what 'can be opened' means.

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 output schema, and no annotations, the description is severely incomplete. It does not explain how the parameters relate to the URL check, what the return value is, or how to interpret results. An agent would not know what to do with parameters like 'city' or 'zone' when checking a URL, making this inadequate for correct invocation.

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?

Although schema description coverage is 100%, the description adds no meaning beyond the schema. More problematically, several parameters (city, feed, json, path, zone, query) seem unrelated to the stated purpose of checking a URL, and the descriptions note they are 'discarded'—creating confusion about the tool's actual scope. The description fails to reconcile the parameter set with the stated function.

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 clear verb ('Check') and resource ('URL'), and includes a distinguishing note ('No browser is launched'). However, the meaning of 'can be opened' is vague—it could refer to HTTP status, DNS resolution, or mere format validation. It does not explicitly differentiate from siblings like 'browser-url-ok' or 'fetch-status', and the negative trait alone is insufficient to fully separate it.

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?

The description provides no guidance on when to use this tool versus alternatives. It neither names any sibling tools nor offers conditions for selection. An agent would have to infer usage from the description and the tool name, which is insufficient.

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