Commodore 64 Ultimate Computer MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Disable a drive' implies a state change (likely from enabled to disabled), but it doesn't specify effects (e.g., does it unmount disks, affect emulation, or require permissions?), reversibility, or error conditions. For a mutation tool with zero annotation coverage, this leaves critical behavioral traits undocumented.

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 'Disable a drive' is extremely concise—three words that directly convey the core action. It's front-loaded with no wasted words, making it easy to parse. For a simple tool with one parameter, this brevity is effective and appropriate.

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 complexity (a mutation operation with no annotations and no output schema), the description is insufficient. It lacks details on behavior, side effects, error handling, or return values, leaving gaps that could hinder correct usage. For a tool that likely changes system state, more context is needed to ensure safe and effective invocation.

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 single parameter 'drive' documented as 'Drive identifier (e.g., 'a', 'b')'. The description adds no additional parameter semantics beyond this, as it doesn't explain format constraints, valid identifiers, or examples. With high schema coverage, a baseline score of 3 is appropriate—the schema does the work, but the description doesn't enhance understanding.

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 'Disable a drive' clearly states the action (disable) and target resource (a drive), making the purpose immediately understandable. It distinguishes from obvious siblings like 'drive_on' (enable) and 'drive_remove' (delete), though it doesn't explicitly differentiate from all drive-related tools like 'drive_set_mode' or 'drive_reset'. The description is specific but could be more precise about what 'disable' entails.

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 prerequisites (e.g., drive must exist or be mounted), exclusions (e.g., cannot disable while active), or compare to siblings like 'drive_on' for enabling or 'drive_remove' for deletion. Without this context, an agent might misuse it or overlook better options.

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