Cross-Platform Filesystem 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. While 'execute a shell command' implies a potentially dangerous operation with security implications, the description doesn't mention permission requirements, security restrictions, whether commands run in a sandbox, or what happens with output/errors. The 'platform-aware' hint is useful but insufficient for a tool that could have significant behavioral consequences.

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 at just 6 words, with zero wasted language. It's front-loaded with the core purpose and includes a useful qualifier. Every word earns its place, making it easy for an agent to parse quickly while still conveying essential information.

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 potentially dangerous execution tool with no annotations and no output schema, the description is inadequate. It doesn't address security implications, permission requirements, error handling, output format, or execution environment. Given the complexity and risk profile of shell command execution, the description should provide much more context about behavioral constraints and expected outcomes.

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 fully documents both parameters. The description doesn't add any parameter-specific information beyond what's in the schema. It doesn't explain what types of commands are supported, format requirements, or how 'platform-aware' affects parameter interpretation. Baseline 3 is appropriate when the schema does all the parameter documentation work.

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 ('execute') and resource ('shell command'), making the purpose immediately understandable. It adds the qualifier 'platform-aware' which provides useful context about cross-platform compatibility. However, it doesn't explicitly differentiate this from sibling tools like 'get_platform_info' or other execution-related tools that might exist.

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 no guidance about when to use this tool versus alternatives. With siblings like 'get_platform_info' and various file operations, there's no indication whether this is for system-level commands, script execution, or how it differs from other tools that might execute code. The agent receives no usage context or exclusion criteria.

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