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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does add one useful fact — 'Page content is not stored' — which signals a privacy-safe operation. However, it does not disclose whether a live HTTP request is made, how redirects are handled, or what happens on failure, which are material for a network-touching tool.

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 compact sentences with the core result front-loaded. The second sentence adds a meaningful privacy constraint without padding. Every word earns its place.

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 four parameters where three (host, json, zone) don't align with the described purpose, the description is incomplete. An agent cannot tell whether those parameters are inputs, outputs, or artifacts of a merged schema. There is no output schema and no explanation of return values beyond the three items mentioned.

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 description coverage is 100%, so the schema already documents each parameter. The description itself adds no parameter meaning. Notably, the schema parameters host, json, and zone appear unrelated to the stated purpose of returning host/scheme/status, creating ambiguity that the description does not resolve.

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 uses a specific verb and resource: 'Return host, scheme, and HTTP status for a URL.' This clearly differentiates it from the validate-json sibling (JSON input) and normalize-url sibling (URL normalization), though it does not explicitly name them. The tool name 'citation' mismatches the described function, which slightly reduces clarity.

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?

There is no guidance on when to use this tool versus normalize-url or validate-json, and no mention of prerequisites or exclusions. The only extra sentence, 'Page content is not stored,' is a behavioral note, not usage guidance.

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