Set project

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

With no annotations provided, the description carries full transparency burden. It explains the required folder contents and the ordering constraint. It does not mention side effects like loading or state changes, but for a selection tool this is sufficient. Minor improvement could note whether it validates the folder.

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 sentences, no unnecessary words. The first sentence defines the action and the resource, the second provides essential usage guidance. Every word serves a purpose.

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 a single required parameter and no output schema, the description fully covers what the tool does, what it expects, and when to use it. It is complete for a setup/configuration tool.

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 coverage is 100% with a clear param description. The description adds value by specifying that the path must be absolute and that the folder must contain Game.rpgproject and data/ directory, providing practical usage context beyond the schema.

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 the tool's purpose: selecting the RPG Maker MV project folder. It specifies the required files (Game.rpgproject and data/) and the action ('Select the folder'). This distinguishes it from all sibling tools, which are for editing or querying specific project elements.

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 description explicitly states when to use this tool: 'Must be called before other tools unless the server was started with --project.' This provides clear context and an alternative condition, offering excellent guidance for correct invocation sequencing.

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