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

With no annotations provided, the description carries the full burden and adds valuable behavioral context: it discloses that the mount is persisted across server restarts, which is a key trait not inferable from the schema. However, it doesn't mention potential errors (e.g., invalid paths) or performance impacts.

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 the core purpose, uses two efficient sentences with zero waste, and includes the alias note as helpful context. Every sentence earns its place by adding clarity without redundancy.

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 low complexity (1 parameter, no output schema, no annotations), the description is mostly complete: it covers purpose, usage, and persistence. However, it lacks details on return values or error handling, which could be useful despite no output schema.

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 meaning beyond what the schema provides, such as examples or constraints, but doesn't contradict it, meeting the baseline for high 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 specific action ('Mount a local folder') and the resource ('.txt and .md files'), distinguishing it from siblings like mount_sqlite or mount_url by specifying file types and local mounting. It also explicitly notes the alias relationship to mount_folder, preventing confusion.

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?

It provides explicit guidance on when to use this tool (for mounting local folders with .txt and .md files) and when not to use it (by implying alternatives like mount_sqlite for databases or mount_url for URLs). The alias note clarifies it's interchangeable with mount_folder, aiding tool selection.

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

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

No annotations are provided, so the description carries the full burden. It mentions the tool lists mounts but does not disclose behavioral traits such as whether it requires permissions, how it handles errors, or the format of the returned list (e.g., structured data or raw text).

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, efficient sentence that directly states the tool's purpose without any wasted words. It is front-loaded and appropriately sized for a simple tool.

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 low complexity (0 parameters, no annotations, no output schema), the description is minimally complete. It states what the tool does but lacks details on output format or behavioral context, which could be helpful for an agent to understand the result.

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 0 parameters with 100% coverage, so no parameter information is needed. The description appropriately does not add parameter details, and the baseline score for 0 parameters is 4, as it avoids unnecessary repetition.

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 ('List') and the resources ('all currently mounted directories, URLs, and databases'), distinguishing it from siblings like 'mount_folder' or 'unmount_folder' which perform different operations on mounts.

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 by specifying 'currently mounted' items, suggesting it should be used to check existing mounts rather than adding or removing them. However, it does not explicitly state when to use this tool versus alternatives like 'query_sqlite' for querying mounted databases.

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

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.

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

With no annotations provided, the description carries full burden and does well by explaining key behaviors: it mounts a database, exposes the schema as MCP resources, and implies this is a setup step for querying. It doesn't mention potential errors (e.g., invalid paths), permissions, or persistence, but covers the core operational context adequately.

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 sentences with zero waste: the first states the purpose and outcome, the second provides usage guidance. It is front-loaded with the main action and efficiently structured without redundancy.

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 is complete enough for a simple setup tool: it explains what the tool does, how it integrates with the system (exposing schema), and the next step (using query_sqlite). It could mention error handling or limitations, but covers the essential context for an AI agent.

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 single 'path' parameter fully. The description adds no additional parameter details beyond what the schema provides, such as file format requirements or examples, meeting 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 action ('Mount'), the resource ('a local SQLite database file'), and the outcome ('Its schema is automatically exposed as an MCP resource'). It distinguishes from sibling 'mount_folder' and 'mount_url' by specifying SQLite databases, and from 'query_sqlite' by being a setup operation rather than a query tool.

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?

Explicitly states when to use this tool ('Mount a local SQLite database file') and when to use an alternative ('Use query_sqlite to run SELECT queries against it'). It differentiates from sibling tools by specifying the exact file type and provides clear guidance on the workflow.

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

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.

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 effectively communicates key behavioral traits: the read-only nature, SELECT-only restriction, JSON output format, and the 100-row limit. These are important constraints that help the agent understand the tool's behavior beyond basic functionality.

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 and front-loaded with all essential information in a single sentence. Every word earns its place, communicating purpose, constraints, and output format without any wasted text. The structure is optimal for agent comprehension.

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?

For a query execution tool with no annotations and no output schema, the description provides good contextual completeness. It covers the read-only nature, query type restriction, output format, and row limit. The main gap is the lack of error handling information or result format details, but given the tool's relative simplicity, this is reasonably complete.

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 schema description coverage is 100%, with both parameters well-documented in the input schema. The description doesn't add any additional parameter semantics beyond what's already in the schema (path to database file, SQL SELECT query). This meets the baseline expectation when schema coverage is complete.

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 ('Execute a read-only SQL query'), resource ('mounted SQLite database'), and scope ('SELECT only'). It distinguishes from siblings like mount_sqlite or list_mounts by focusing on query execution rather than database management operations.

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 about when to use this tool: for read-only SELECT queries against mounted SQLite databases. However, it doesn't explicitly mention when NOT to use it (e.g., for write operations) or name specific alternatives among siblings, though the SELECT-only restriction implies alternatives would be needed for other operations.

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

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

No annotations are provided, so the description carries the full burden. It discloses that unmounting makes files 'no longer exposed as resources', which hints at a destructive effect, but it does not specify whether this action is reversible, requires permissions, or has side effects like data loss. More behavioral details are needed for a mutation tool.

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, well-structured sentence that front-loads the action ('Unmount a previously mounted folder') and efficiently explains the outcome. Every word contributes to understanding, with no wasted text, making it highly concise and clear.

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 has no annotations and no output schema, the description is minimal but covers the basic purpose. However, for a destructive operation like unmounting, it lacks details on behavior, error handling, or output expectations, leaving gaps in completeness for safe agent use.

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%, with the parameter 'path' documented as 'Absolute path of the folder to unmount'. The description adds no additional meaning beyond this, as it does not explain parameter syntax or constraints. With high schema coverage, the 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 clearly states the specific action ('unmount') and resource ('a previously mounted folder'), and distinguishes it from siblings like 'mount_folder' and 'list_mounts' by specifying the opposite operation. It explicitly mentions the outcome ('so its files are no longer exposed as resources'), which further clarifies its purpose.

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 by referencing 'a previously mounted folder', suggesting it should be used after mounting, but it does not explicitly state when to use this tool versus alternatives like 'list_mounts' to check mounts first. No exclusions or clear alternatives are provided, leaving some ambiguity in context.

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