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

With no annotations provided, the description carries the full behavioral burden. 'Audits' and 'generates ... recommendations' accurately convey a non-mutating analysis tool that produces output, and the specific audit subject (orphan pages, anchor text) adds useful context beyond the tool name. However, it does not disclose process, response shape, crawl behavior, or any limits, so it is not fully transparent.

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?

A single, front-loaded sentence that lists the audited elements and the produced outcome without filler or redundancy. Every phrase contributes meaning, making the definition efficient and scannable.

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 one-parameter, non-mutating audit tool, the description covers what it analyzes, what it produces, and the schema specifies how to supply the target. It does not specify output formatting or detailed usage caveats, but nothing critical is missing for an agent to select and invoke the tool.

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 only parameter, target, already carries a clear schema description ('Target file path or live URL'), so schema coverage is 100% and the description adds no additional meaning. The baseline of 3 is appropriate because the schema does the semantic heavy lifting and no ambiguity exists.

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 states a specific verb ('audits') and resource ('internal link architecture, generic anchor text, orphan pages'), and it names the output ('high-value contextual linking recommendations'). Together with the tool name, this clearly distinguishes it from the many sibling seo_audit_* tools.

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 implies the tool is for diagnosing internal-link health and generating linking suggestions, but it never states when to prefer it over alternatives such as seo_audit_technical or seo_audit_onpage. There are no explicit exclusions or alternative tool pointers, so the context is only inferred.

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