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

No annotations exist, so the description carries the full burden and does so well: it discloses the conflict behavior (nothing changed, conflict file list returned), that failure modes leave the session active and retryable, and that failures surface as reason= discriminators (conflict / head_kept / head_mismatch). This is exactly the kind of state/side-effect detail an agent needs before mutating a session.

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?

Front-loaded with the core action, then the alternative, then failure semantics. Every sentence earns its place, though the final parenthetical stacks three discriminators and two remediations into one dense clause.

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?

An output schema exists, so return-value enumeration is unnecessary; combined with the description's coverage of conflict handling, retryability, and discriminator reasons, an agent has everything needed to invoke and interpret the call correctly.

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 coverage is 0% and the description never mentions project_id, so it adds no meaning beyond the schema. With a single, self-evident identifier parameter this is a minor gap rather than a critical one, landing at the baseline rather than above or below it.

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 and resource ('Adopt the project's parked AI session') and immediately elaborates the concrete effect: merging the session branch into the default branch and handing HEAD over. It is clearly distinguishable from abandon_session, which is named explicitly.

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?

Gives an explicit selection rule: 'Use instead of abandon_session when the session's work should be kept,' plus a fallback path ('or fall back to abandon_session') when resolution fails. Both the when and the when-not are covered.

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