load_disc

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

No annotations are present, but the description details side effects: whether the host file is modified, the read-only default, and the lack of reset/autoboot. It also specifies valid drive values (0 or 1).

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 three focused paragraphs, each sentence contributing to usage, side effects, or alternatives. It is well-structured and free of redundant content.

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?

Despite no annotations and zero schema descriptions, the description covers all critical behavioral traits, parameter semantics, and alternative tools, making it fully actionable for an AI agent.

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 description explains the meaning of drive, writeable, and mutable, including defaults and the relationship between mutable and writeable. It does not explicitly detail disc or session_id, but the overall context and self-evident naming make them clear.

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 'Mount a disc image into the named drive at runtime' with a specific verb and resource, and further distinguishes itself by noting it does not trigger reset/autoboot, contrasting with boot_disc.

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?

It explicitly describes when to use this tool versus boot_disc, including a composed alternative with reset(autoboot=True). It also clarifies that mutable requires writeable, giving clear usage conditions.

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