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

The description states 'Page content is not stored,' which is a behavioral trait, but it does not disclose other significant behaviors such as the discarding of several parameters (ref, city, feed, json, path, query) as indicated in the schema. With no annotations, the description carries the full burden, but it omits these side effects and does not clarify the return format or error behavior.

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, front-loaded sentence that directly states the core function. It is efficient and avoids padding, though it could benefit from a bit more detail. Given its brevity, it earns a high conciseness score.

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?

The tool has 9 optional parameters, no annotations, and no output schema. The description only covers the core return values (host, scheme, HTTP status) and one behavioral note. It does not explain the purpose of the many parameters (ref, city, feed, json, path, query, zone, etc.), nor when to use it over siblings, nor the response structure. This is grossly inadequate for the tool's complexity.

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 schema has 100% coverage with descriptions for all 9 parameters, so the baseline is 3. The tool description does not add any additional meaning to the parameters; it only mentions 'URL' generically without referencing specific parameters. Since the schema already documents each parameter, the description does not need to compensate, but it also adds no extra value.

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 clearly states the tool's function: 'Return host, scheme, and HTTP status for a URL.' This is a specific verb+resource. However, it does not differentiate from sibling tools like fetch-status or web-fetch that might also return HTTP status, so it lacks explicit differentiation. The name 'citation' is vague but the description clarifies the action.

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 alternatives. It does not mention any conditions, exclusions, or comparison to siblings like fetch-status, normalize-url, or web-fetch. The description only states what it returns, not when it is preferred.

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