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

With no annotations, the description carries the full burden of explaining side effects and guarantees. It does disclose that page content is not stored, which is helpful, but it omits other behavioral details such as error handling, authentication requirements, or rate limits.

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 compact and front-loaded with the primary purpose, and the second sentence adds a meaningful privacy guarantee. It is efficient, though the extreme mismatch between the terse description and the nine optional parameters makes it feel underspecified.

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 complexity of the schema with nine unrelated optional parameters, the description is not complete enough for an agent to invoke the tool correctly. It does not explain the role of most parameters, the expected output format, or how they relate to the stated URL-focused function.

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 the schema has 100% description coverage, most parameter descriptions are unrelated to the stated purpose of returning host, scheme, and HTTP status for a URL. Params like city, zone, json, and path appear to reference other tools' concerns, and the main description does not clarify how they should be used.

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 core action—return host, scheme, and HTTP status for a URL—and adds a useful limiting detail that page content is not stored. It does not explicitly reconcile this narrow purpose with the tool's name 'citation' or the much broader parameter set, but the primary function is understandable.

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 gives no explicit guidance on when to prefer this tool over sibling tools such as fetch-status, normalize-url, or web-fetch. It only states a negative behavior ('page content is not stored'), leaving the agent to infer the appropriate use case.

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