List links from a page (sitemap/RSS-first)

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

Beyond the readOnlyHint annotation, the description adds meaningful behavior: it prefers sitemap/RSS/Atom feeds to minimize impact and falls back to extracting in-page links. This discloses the tool's operational strategy without contradicting annotations.

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 sentence that front-loads the purpose, mentions the low-impact nature, and describes the strategy. There is no filler or redundancy.

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 simple two-parameter read-only tool with no output schema, the description explains the core behavior (feed-first fallback to in-page) and impact level. It could mention output shape, but that's not critical for a list-returning 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 schema already provides 100% coverage for both parameters (url and filter) with clear descriptions. The tool description does not add parameter-specific context, maintaining the baseline for schema-heavy tools.

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?

Title clearly states 'List links from a page', and description specifies 'link discovery' with a concrete strategy (prefers sitemap/RSS/Atom, else in-page). This distinguishes it from siblings fetch and screenshot.

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?

Description conveys clear usage context ('low-impact', feed-first strategy) implying when to use it for light-weight link harvesting. However, it does not explicitly name alternatives or exclusion criteria, so it stops short of a 5.

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