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

With no annotations, the description must disclose side effects; it only says 'Page content is not stored,' which addresses retention but not network behavior, read-only guarantees, or failure modes. This is insufficient transparency for a tool that fetches URLs and returns HTTP status.

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 brief and front-loaded, but it is too sparse for the apparent complexity of four unrelated parameters. The second sentence adds a privacy note but does not help structure the tool's behavior or parameter usage.

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?

With no output schema, no annotations, and a mismatch between the description and parameters, the agent lacks critical context about return format, parameter combinations, and error behavior. The description is far from complete for reliable 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 all parameters have descriptions, they are disconnected from the tool's stated purpose: json is for validation and zone is a timezone, both irrelevant to returning host, scheme, and HTTP status. The descriptions do not explain how these parameters relate to each other or to the tool's core 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 names a concrete action and output ('Return host, scheme, and HTTP status for a URL'), so the primary purpose is somewhat clear. However, the tool name 'citation' and the unrelated parameters (json, zone) make the intended scope ambiguous.

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 guidance on when to use this tool instead of its siblings, such as normalize-url, status-catalog, validate-json, or timezone. It states what it returns but not the conditions or use cases for choosing it.

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