Commodore 64 Ultimate Computer MCP Server

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Reset' implies a mutation that may alter drive state, but it doesn't specify if this is destructive (e.g., clears data), requires specific permissions, has side effects on mounted disks, or what the expected outcome is. This leaves critical behavioral traits unclear 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 a single, efficient sentence with zero waste—'Reset a specific drive' is front-loaded and directly conveys the core purpose without unnecessary elaboration, making it highly concise and well-structured.

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 complexity of a reset operation with no annotations and no output schema, the description is incomplete. It doesn't explain what 'reset' does behaviorally, what to expect as a result, or any error conditions, leaving significant gaps for an AI agent to understand and invoke the tool correctly.

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 schema description coverage is 100%, with the parameter 'drive' documented as a drive identifier (e.g., 'a', 'b'). The description adds no additional meaning beyond this, such as valid drive ranges or examples, but the schema adequately covers the parameter semantics, meeting the baseline for high coverage.

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 'Reset a specific drive' clearly states the action (reset) and target (drive), but it's vague about what 'reset' entails—whether it's a soft reset, hard reset, or clearing data. It distinguishes from siblings like 'drive_remove' or 'machine_reset' by focusing on drives, but lacks specificity on the reset type.

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?

No guidance is provided on when to use this tool versus alternatives like 'drive_remove', 'machine_reset', or 'reset_config_to_default'. The description doesn't mention prerequisites, such as whether the drive must be on or mounted, or any exclusions for its use.

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