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

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds valuable behavioral context: it prefers sitemap.xml/RSS/Atom feeds when available, otherwise extracts in-page links. This explains the underlying 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?

The description is a single, concise sentence that efficiently conveys the tool's behavior. There is no unnecessary information, and the title preceding it adds clarity.

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 tool's simplicity (2 parameters, no output schema) and the presence of annotations, the description covers all essential aspects: what it does, how it works, and its low-impact nature. The agent has enough information to decide when and how to use it.

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 coverage is 100% with both parameters (url, filter) described. The tool description does not add further meaning to the parameters beyond what the schema provides. Baseline score of 3 is appropriate.

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 explicitly states the tool's purpose: low-impact link discovery preferring sitemap/RSS/Atom feeds, falling back to in-page links. The title 'List links from a page (sitemap/RSS-first)' reinforces the specific resource and method, clearly distinguishing it from siblings like fetch (raw content) and screenshot (visual capture).

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 provides clear context: it is a low-impact tool for discovering links, preferring structured feeds. While it does not explicitly name alternatives or state when not to use it, the context and sibling names (fetch, screenshot) imply that for raw page content or screenshots, other tools are appropriate.

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