Desktop Commander 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 context about the return values (base64 encoded data and MIME type) and the directory restriction, which are useful beyond basic functionality. However, it lacks details on permissions, error handling, or performance aspects, leaving gaps for a tool with no annotation coverage.

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 appropriately sized with three concise sentences that are front-loaded: it states the action, return values, and constraint efficiently. Every sentence adds value without redundancy, 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 no annotations, no output schema, and low schema coverage, the description provides basic completeness by covering purpose, returns, and a constraint. However, for a tool that reads media files, it lacks details on supported formats, size limits, or error cases, which are important for contextual understanding. It's adequate but has clear gaps.

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 1 parameter with 0% description coverage, so the description must compensate. It doesn't explicitly mention the 'path' parameter or provide additional semantics beyond the directory constraint implied in the description. The baseline is 3 since the schema coverage is low, but the description adds minimal param-specific value.

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 verb 'Read' and resource 'image or audio file', specifying the action and target. It distinguishes from siblings like 'read_file' and 'read_text_file' by focusing on media files, though it doesn't explicitly contrast them. The purpose is specific but could be more precise about sibling differentiation.

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 stating 'Only works within allowed directories', providing some context about constraints. However, it doesn't explicitly guide when to use this tool versus alternatives like 'read_file' or 'read_text_file', nor does it mention prerequisites or exclusions beyond the directory restriction. Usage is implied but not fully articulated.

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