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 full burden for behavioral disclosure. While 'Change' implies a mutation, it doesn't specify whether this requires specific permissions, whether changes are immediate or require a reboot, what happens to mounted disks during the change, or what error conditions might occur. This leaves significant behavioral gaps for a mutation tool.

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 perfectly concise - a single sentence with zero wasted words that immediately communicates the core functionality. It's front-loaded with the essential action and includes the specific mode options without unnecessary elaboration.

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 mutation tool with no annotations and no output schema, the description provides basic purpose but lacks critical context about behavioral implications, error handling, and system state changes. While the purpose is clear, the description doesn't adequately address what an agent needs to know about using this tool safely and effectively.

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 documents both parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain parameter relationships, constraints, or provide examples. The baseline score of 3 reflects adequate but minimal value addition.

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 action ('Change') and resource ('drive type') with specific options (1541/1571/1581), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'set_config_item' or other drive-related tools, which prevents a perfect score.

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. With multiple drive-related tools in the sibling list (e.g., drive_on, drive_off, drive_reset, mount_disk_file), there's no indication of when this specific mode-change operation is appropriate versus other drive operations.

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