install_godot_editor_bridge

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

With no annotations, the description carries the full burden, and it does disclose the concrete side effects: add-on files are written into the project, the bridge port is configured, project.godot is modified, and a restart is required. It omits failure/idempotency behavior (what happens if the bridge is already installed), whether it overwrites existing config, and any permission or editor-state constraints.

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 compact sentences, front-loaded with the core action and followed by the required follow-up step; no filler. The unbacked port clause is the only slightly wasted/ambiguous element.

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 filesystem-mutating setup tool with no annotations and no output schema, the description covers the main effects and the restart requirement but says nothing about return values, idempotency, or how partial failures are handled. It is adequate but leaves real gaps for an agent invoking it unattended.

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 description coverage is 100%, so both parameters (projectPath, overwrite) are already documented in the schema; the description adds no parameter-level detail. It also mentions 'configure its localhost bridge port' even though no port parameter exists, which is mildly confusing but not a schema contradiction.

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?

Specific verb-plus-resource chain: installs the Godot editor add-on, configures its bridge port, and enables it in project.godot. An agent can distinguish it from siblings like inject_script_autoload or generate_tscn_scene, though the description never explicitly contrasts itself with them.

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?

Usage is implied rather than stated: it reads as a one-time setup step, and the closing sentence gives the post-install action (restart the editor). There is no explicit when-to-use, no prerequisites (e.g. whether the editor must be closed), and no comparison to related siblings that also modify the project.

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