detach_project

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

Annotations (destructiveHint=true, idempotentHint=true) already indicate mutation and safety. Description adds critical context: 'Does NOT stop the manually launched Godot process — that stays running.' This goes beyond annotations, but the high annotation coverage lowers the burden slightly.

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?

Four sentences, no filler. Front-loaded with core action. Every sentence adds value (use case, limitations, alternatives, no-op behavior). Ideal length.

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 no output schema, description fully covers what the tool does, when to use it, what it does not do, and its safety properties. Includes no-op condition. No gaps.

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?

Input schema has 0 parameters with 100% coverage, so no parameter description needed. Baseline for zero parameters is 4; description appropriately focuses on behavior.

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?

Clear verb+resource: 'Clear attached-mode runtime state and remove the injected McpBridge autoload.' Distinguishes from sibling: 'For spawned sessions (run_project), use stop_project instead.' Specific and unambiguous.

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 when to use ('after attach_project when you are done driving the game from MCP'), when not to use ('For spawned sessions...use stop_project'), and that it is a no-op if no attached session exists. Provides complete guidance.

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