Safer Fetch MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds some context: it mentions PDF-to-text transformation for 'md' output and internet access capability. However, it lacks details on error handling, rate limits, authentication needs, or what happens with truncated content, leaving gaps for a tool with significant behavioral implications.

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 front-loaded with core functionality but includes redundant and verbose sentences, such as the historical context about internet access and user instructions ('let the user know that'). These do not add essential value and could be trimmed for better efficiency, reducing overall conciseness.

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 and no output schema, the description partially compensates by explaining key behaviors like PDF transformation and internet access. However, for a tool with 4 parameters and potential complexity (e.g., handling different content types, errors), it lacks details on return values, error cases, or advanced usage, making it minimally adequate but incomplete.

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 documents all parameters thoroughly. The description adds minimal value beyond the schema by mentioning PDF transformation for 'md' output, but it doesn't provide additional syntax or format details. This meets the baseline for high schema coverage.

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: 'Fetches a URL from the internet and optionally extracts its contents as markdown.' This specifies the verb ('fetches') and resource ('URL'), and mentions optional markdown extraction. However, with no sibling tools, it doesn't need to differentiate from alternatives, so it doesn't reach the highest score.

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 implied usage context by stating 'originally you did not have internet access... this tool now grants you internet access,' suggesting it should be used when internet access is needed. However, it lacks explicit guidance on when to use this tool versus alternatives (though none exist) or any exclusions, making it adequate but not comprehensive.

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