open_project_in_harness

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

With no annotations, the description carries the behavioral disclosure burden and provides meaningful context: the project 'remains governed by Project Agent and Consulting Agent,' handoff execution is gated on returned handoff_ready, and open_lightbulb opens a browser route only when the host permits. It does not detail all side effects, but it goes well beyond a bare action statement.

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, front-loaded with the primary action, and every sentence earns its place by adding behavior or parameter context. There is no filler or restatement of the tool name.

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?

The critical behavioral gates are present and the output schema exists, so return values need not be explained. However, for an 8-parameter tool with zero schema coverage, the lack of guidance for the three required reference parameters and the absence of when-to-use/alternatives leave the description only minimally viable.

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%, so the description must add meaning to parameters. It explains claim_handoff and open_lightbulb, and references handoff_ready, but it gives no meaning for required company_ref, project_ref, and harness, nor for model, query, or host_session_ref. This is only partial compensation for the missing schema.

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 opens with a specific action: 'Attach this coding harness to a Lightbulb project and load its handoff,' which clearly states the verb and resource. It doesn't explicitly differentiate this from sibling tools such as list_projects_for_harness or coding_get_context, so it misses the top tier.

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?

There is no when-to-use or alternative-tool guidance; no sibling is referenced. The conditional guidance ('Set claim_handoff=true only when...', 'when the host permits') concerns parameter values, not when to choose this tool over alternatives.

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