load_project

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

No annotations are provided, so the description carries the full burden of disclosure. It only says 'load' without describing side effects, error handling, required permissions, or return behavior. This is insufficient for a tool that may affect the state of the environment.

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, front-loaded sentence with no fluff. It is appropriately concise for a simple tool.

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?

The tool is simple, but without an output schema or annotations, the description fails to mention what happens after loading (e.g., return value, whether the project becomes the active context for other tools). This leaves the agent to infer important behavioral context.

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 describes the only parameter, 'path', as 'Project directory path' with 100% coverage. The description adds no extra semantic detail beyond what the schema provides, which aligns with the baseline score for high schema 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 uses a specific verb ('load') and clearly identifies the resource ('existing RPG Maker MZ project'). It distinguishes from sibling tool 'create_project' by emphasizing 'existing', which implies loading vs creating.

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 phrase 'existing project' implies that this tool is for loading previously created projects, not for creating new ones. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention any prerequisites (e.g., that a project must be loaded before using other tools).

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