Omni-MCP

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

With no annotations provided, the description carries the full burden and does well by disclosing key behavioral traits: it fetches web pages, converts HTML to Markdown, exposes content as an MCP resource, caches results, and persists across server restarts. This covers read/write implications, persistence, and performance aspects without contradictions.

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 and highly concise, with two sentences that efficiently cover purpose, process, and behavioral traits without any wasted words. Each sentence adds critical value, making it easy to parse and understand quickly.

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 moderate complexity (fetching and converting web pages) and no annotations or output schema, the description is largely complete: it explains what the tool does, key behaviors like caching and persistence, and the input parameter. A minor gap is lack of error handling or output format details, but it's sufficient for basic understanding.

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 input schema has 100% description coverage, clearly documenting the single 'url' parameter. The description does not add meaning beyond the schema (e.g., no details on URL validation or error handling), so it meets the baseline of 3 for high schema coverage without extra parameter insights.

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 specific verbs ('fetch', 'convert', 'expose') and resource ('web page'), and distinguishes it from siblings like mount_folder and mount_sqlite by specifying it handles URLs and HTML-to-Markdown conversion. It goes beyond the name 'mount_url' by explaining the full transformation process.

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 usage for web pages needing HTML-to-Markdown conversion and persistence, but does not explicitly state when to use this tool versus alternatives like mount_folder (for local files) or add_new_source (purpose unclear). It provides some context but lacks explicit guidance on exclusions or comparisons with siblings.

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