attach_project

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

Describes wait time (up to 15s), response format (plain-text with port), and error condition when called late. Annotations have destructiveHint: true which aligns with description's injection action.

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?

Concise yet comprehensive: key action first, then guidelines, then fallback/cleanup. No superfluous sentences.

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 adequately specifies return type. Covers timing, failure, parallelization, and cleanup. No missing critical details for a moderate-complexity 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?

Adds meaning beyond schema: bridgePort auto-selects if omitted, and the port is baked into mcp_bridge.gd at inject time. Schema already has 100% coverage but description enriches understanding.

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?

Clearly states the tool injects the MCP bridge into a user-launched Godot process and waits for a response. Distinguishes from sibling run_project by noting prefer run_project unless MCP must not spawn Godot.

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 says call BEFORE Godot launches, recommends parallel launch pattern, and suggests detach_project/stop_project for cleanup. Mentions prefer run_project as alternative when Godot can be spawned.

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