Install bridge addon

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

The description discloses that the tool installs/refreshes the addon and its autoload, aligning with the idempotentHint annotation. It adds no further behavioral details beyond what the annotation already provides, so the value added is minimal.

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 extremely concise with two sentences, front-loading the verb and resource. Every sentence adds value with no wasted words.

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 the tool's simplicity (1 parameter, no output schema, idempotent annotation), the description is complete. It covers purpose, usage context, and needed details without 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?

With only one parameter and 100% schema description coverage, the description adds no additional meaning beyond the schema. The baseline score of 3 is appropriate as the schema already documents the parameter thoroughly.

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 'Install (or refresh)' and the specific resource 'godot_mcp live-control bridge addon and its autoload'. It distinguishes from sibling tools by noting that godot_setup or godot_run normally handle this, making the purpose explicit.

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 indicates that this tool is normally handled by godot_setup or godot_run but is available explicitly. This provides clear context for when to use it. However, it does not list specific conditions for when not to use it, but the idempotent hint mitigates that gap.

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