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

With no annotations present, the description carries the behavioral disclosure burden. 'Page content is not stored' is a useful privacy-related behavioral trait, but the description does not disclose network side effects, timeouts, error behavior, or any access requirements. It is minimally transparent but not comprehensive.

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 two short sentences, front-loading the core purpose and adding one relevant safety note. There is no filler or redundant restatement of the tool name.

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 a seven-property schema, no output schema, and no annotations, yet the description covers only the URL case. It omits the role of the remaining parameters, the return shape, and error handling, making it incomplete 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?

The input schema already provides descriptions for all seven parameters, so the baseline is 3. The description only reinforces that 'url' is the primary input and adds no clarity about whether the other parameters are required, alternative modes, or intended decoys.

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 a specific result—host, scheme, and HTTP status—for a URL, which is more than a tautology. However, the tool name 'citation' and the presence of six other unrelated schema parameters are not reconciled, and there is no differentiation from sibling URL/status tools like fetch-status or normalize-url.

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 when-to-use or when-not-to-use guidance, nor any comparison against alternatives. An agent must infer that this tool is appropriate whenever host/scheme/status for a URL is needed, and the noisy schema only increases the ambiguity.

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