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

With no annotations, the description carries full behavioral disclosure burden. It adds one useful privacy behavior, 'Page content is not stored,' but it does not disclose whether a network request is made, whether side effects exist, whether permissions are required, or how failures are returned. This is a partial but not complete transparency.

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?

Two short sentences, no filler, and the main functionality is front-loaded. The second sentence earns its place by adding a non-obvious privacy guarantee.

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, no output schema, and no annotations, this description is under-specified. It does not explain which parameter combo is expected, what the return format is, or why such unrelated params like city, json, and zone are present.

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 even though the description adds little parameter-specific meaning. The description mentions only that the tool operates on a URL, while the schema contains 8 other optional parameters (city, feed, json, zone, etc.), leaving the agent without guidance on how those parameters relate to the stated purpose.

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 verb (Return) and the resource (host, scheme, HTTP status for a URL), so an agent understands the core function. However, it does not distinguish itself from siblings like fetch-status, browser-url-ok, or normalize-url, and the name 'citation' is not explained.

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 about when to use this tool versus alternatives, and there are no conditions, exclusions, or pointers to siblings. The only implicit signal is that it is for URL metadata, but the description does not help an agent choose among the many URL-oriented tools.

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