connect_project

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

With no annotations, the description carries full burden and does disclose meaningful side effects: it installs a bridge, creates a backup, and requires restarting UE afterward. However, it omits permissions/auth requirements, whether existing bridge configs are overwritten, and any rate or failure behavior.

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?

Three short sentences, front-loaded with the core action and followed by the client-specific path formats and the restart caveat. Efficient with little waste, though the second sentence could be slightly more explicit about which parameter it describes.

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 3-parameter mutation-style tool with no annotations and no output schema, the description covers the main action, path formats, and the restart requirement, but leaves install_bridge and blender_path unexplained and gives no return or verification information.

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 0% for 3 parameters. The description compensates partially by explaining the required project_path's format differs per client (Unity folder vs UE folder/.uproject), but blender_path and install_bridge are never addressed, leaving a real gap.

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?

States a specific verb (Connect) and resource (project) and clarifies it covers both Unity and UE clients plus bridge installation with backup. It does not explicitly contrast itself with siblings like list_projects or inspect_target, but the client/bridge scope is distinctive enough to identify it.

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 explicit when-to-use or when-not-to-use guidance, and no alternatives named. The Unity/UE folder-format note implies the tool's context but never states prerequisites (e.g., that a project must already exist or when to prefer this over other project tools).

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