Omni-MCP

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

With no annotations provided, the description carries full burden. It discloses key behavioral traits: the mount persists across server restarts and only .txt/.md files become readable resources. However, it doesn't mention permission requirements, error conditions (e.g., invalid paths), or what 'readable resources' means in practice (e.g., access methods).

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?

Two concise sentences with zero waste: the first states the purpose and scope, the second adds critical behavioral context (persistence). Every word earns its place, and information is front-loaded appropriately.

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 one parameter with full schema coverage and no output schema, the description is reasonably complete for a mounting operation. It covers the core action, file type constraints, and persistence. However, it lacks details on error handling, performance implications, or integration with sibling tools like 'list_mounts' or 'unmount_folder'.

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 the 'path' parameter fully. The description adds no additional parameter semantics beyond what the schema provides (e.g., no examples of valid folder structures or file limitations). Baseline 3 is appropriate when schema does the heavy lifting.

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 specific action ('mount'), the resource ('a local folder'), and the effect ('.txt and .md files become readable resources'). It distinguishes from siblings like 'mount_sqlite' and 'mount_url' by specifying folder mounting with text/markdown file support.

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 context (making local text/markdown files accessible) and mentions persistence across restarts, which is useful guidance. However, it doesn't explicitly state when to use this versus alternatives like 'mount_sqlite' or 'mount_url', or when not to use it (e.g., for non-text files).

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