MCP Web Scrape

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it mentions checking accessibility and getting HTTP status codes, it lacks critical details like timeout behavior, error handling, rate limits, authentication requirements, or what constitutes 'accessible'. For a network operation tool with zero annotation coverage, this is insufficient.

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 extremely concise (one sentence) and front-loaded with the core functionality. Every word earns its place with no wasted text or unnecessary elaboration.

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 no annotations, no output schema, and a network operation tool that interacts with external systems, the description is incomplete. It should address behavioral aspects like timeouts, error conditions, response format, and limitations. The current description provides only basic functional intent without operational context.

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 fully documents both parameters (url and followRedirects). The description doesn't add any meaningful parameter semantics beyond what's in the schema - it doesn't explain URL format requirements, redirect behavior implications, or status code interpretation. Baseline 3 is appropriate when schema does all the work.

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 the tool's purpose with a specific verb ('check') and resource ('URL'), specifying what it does (check accessibility and get HTTP status codes). However, it doesn't explicitly distinguish itself from sibling tools like 'check_broken_links' or 'monitor_uptime', which might have overlapping functionality.

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 no guidance on when to use this tool versus alternatives. With many sibling tools available (like check_broken_links, monitor_uptime, scan_vulnerabilities), there's no indication of specific use cases, prerequisites, or exclusions for this URL status checking tool.

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