Desktop Commander MCP Server

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: it discloses error handling ('provides detailed error messages'), encoding support ('Handles various text encodings'), and operational constraints ('Only works within allowed directories'). It doesn't mention performance characteristics like rate limits or file size limits, but covers core behavioral aspects 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?

The description is efficiently structured: first sentence states core purpose, second adds behavioral context, third provides usage guidance, fourth explains parameter usage, and fifth states constraints. Every sentence adds value with zero redundancy, and key information is front-loaded.

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 read operation with 3 parameters and no output schema, the description is quite complete: it covers purpose, usage, parameters, constraints, and error behavior. The main gap is lack of output format details (what the returned text looks like, encoding specifics), but given it's a text read tool, this is partially mitigated by the clear purpose statement.

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 67% (2 of 3 parameters have descriptions). The description adds significant value: it explains the purpose of 'head' and 'tail' parameters ('read only the first N lines'/'read only the last N lines'), which the schema descriptions only partially cover. However, it doesn't explain the 'path' parameter beyond what's implied, leaving some semantic gap.

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 ('Read the complete contents'), resource ('a file from the file system'), and scope ('as text'). It distinguishes from siblings like 'read_file' (which might handle binary) and 'read_multiple_files' (which handles multiple files) by specifying text-only, single-file operation.

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?

Explicit guidance is provided: 'Use this tool when you need to examine the contents of a single file.' It also distinguishes from alternatives by mentioning 'head' and 'tail' parameters for partial reading, and clarifies scope with 'Only works within allowed directories' (contrasting with unrestricted file access tools).

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