load_project

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

With no annotations, the description carries the full behavioral burden. It clearly communicates a state-changing, prerequisite nature by stating it must be called before other tools. However, it does not disclose whether it fails on invalid paths, whether it returns project data, or any side effects.

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?

Two short sentences with zero waste. The prerequisite requirement is front-loaded after the purpose, making it easy to scan and understand.

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 single-parameter initialization tool with no output schema and no annotations, the description provides everything needed: what it does and that it must be called first. No significant gaps remain.

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 already provides a complete description for projectPath ('Absolute path to the RPG Maker MZ project directory') at 100% coverage. The description adds no further parameter meaning beyond what the schema provides, so a baseline 3 is appropriate.

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 states a clear verb and resource: 'Load an existing RPG Maker MZ project.' This distinguishes it from creation (create_project) and read-only tools. However, it does not explicitly differentiate itself from sibling tools like get_project_info or list_resources, which also operate on projects.

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?

Explicitly states 'Must be called before using other tools.' This provides unambiguous when-to-use guidance and establishes the tool as a prerequisite, which is critical for correct invocation order.

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