Smart Shell 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 states the tool 'shows' how a command would be adapted, implying it's a read-only, informational operation without execution. However, it doesn't disclose important behavioral traits such as whether it requires specific permissions, how it handles invalid commands, what format the adaptation is shown in, or any rate limits. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 with a single, clear sentence that front-loads the core purpose. There's no wasted language or redundancy, making it efficient and easy to parse. Every word earns its place by directly contributing to understanding the tool's function.

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 (adapting commands across OSes), no annotations, no output schema, and low parameter coverage, the description is incomplete. It doesn't explain what the adaptation output looks like, how OS detection works, error handling, or practical use cases. For a tool that likely returns formatted command strings, the lack of output information is particularly problematic, leaving users guessing about results.

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 mentions 'generic command' which relates to the rawCommand parameter, adding some semantic context. However, it doesn't explain what constitutes a 'generic command' (e.g., cross-platform syntax), provide examples, or detail constraints. This minimal information is insufficient to fully understand parameter usage beyond the schema's basic type definition.

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: to show how a generic command would be adapted for the current OS. It specifies the verb 'show' and the resource 'generic command', making it understandable. However, it doesn't explicitly distinguish this from sibling tools like executeCommand (which runs commands) or getProjectCommands (which retrieves stored commands), leaving room for improvement in 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 provides no guidance on when to use this tool versus alternatives. It doesn't mention scenarios like needing OS-specific command syntax, comparing to executeCommand for actual execution, or using getProjectCommands for retrieving stored commands. This lack of context makes it unclear when this tool is the appropriate choice among the available options.

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