program_load

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 mentions the side effect of loading and optionally starting, but does not disclose what happens to the current session state, whether prior programs are overwritten, what file types are supported, or what errors may occur.

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 concise sentence with no filler. It front-loads the primary action and includes the optional start behavior, though it could have used the saved space to add more useful guidance.

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?

This is a state-changing emulator tool with no annotations and a terse description. It lacks important invocation context such as file type expectations, behavior when autoStart is false, relationship to execute, and what the tool returns when loading fails. The existence of an output schema reduces the need to describe return values, but invocation semantics remain incomplete.

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 67%, with autoStart and fileIndex already documented in the schema. The description adds only the general idea that a C64 program is loaded and optionally started, which is a mild clarification for the undocumented filePath parameter but does not explain format, image behavior, or fileIndex usage.

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 uses a specific verb and resource: 'Loads a C64 program' and adds the optional start behavior. It is clearly distinct in purpose from siblings like memory_read or breakpoint_set, though it does not explicitly differentiate itself from execute as a sibling alternative.

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 given about when to use this tool versus alternatives such as execute or memory_write. The phrase 'optionally starts it' hints at behavior but does not describe when autoStart should be true or false, nor when another tool would be more appropriate.

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