stop_project

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

The description states 'stop', which implies destruction, but does not disclose behavioral traits like whether it is safe (e.g., graceful shutdown), what happens to unsaved data, or if it requires authentication. Annotations provide no additional context.

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 sentence of five words, extremely concise and front-loaded with the essential action. No unnecessary details.

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 simple stop action with no parameters or output schema, the description is adequate but lacks context about when it is applicable (e.g., after a project is started with 'run_project') or what state the project will be in after stopping.

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?

There are no parameters, and the schema coverage is 100% (vacuously). The description does not need to add parameter information, so the baseline of 4 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 clearly states the verb 'Stop' and the resource 'the currently running Godot project', making it specific. However, it does not differentiate from the sibling tool 'godot_stop', which may perform a similar action, slightly reducing clarity.

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 provided on when to use this tool versus alternatives like 'godot_stop' or 'run_project'. There is no mention of preconditions, such as requiring a project to be running, or when not to use it.

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