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

Annotations already indicate readOnlyHint=false, destructiveHint=true, and idempotentHint=false. The description adds meaningful context beyond those flags: the tool is manual-only, may require write-tier manager approval, re-dispatch behavior with force, and why approve no longer auto-opens. No contradiction with annotations.

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 longer than average, but each sentence earns its place: manual-only guardrail, historical rationale, routing preference, exclusions, and approval timing. It is front-loaded with the core verb and object; the parentheticals are dense but not wasteful.

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 mutation with three simple parameters and no output schema, the description provides the operational context that cannot be inferred from the schema: manual-only, approval workflow, routing preference, and when not to use it. The remaining unknowns are not needed to select and invoke the tool 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 description coverage is 100%, and the schema already documents request_id, force, and companyId clearly. The description adds no parameter-level detail beyond referring to the request context, so the baseline of 3 is appropriate.

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 names a specific action ('open'), a specific artifact ('draft GitHub PR shell'), and a precise eligibility ('approved FreedomOS product request'). It also distinguishes this from the older auto-open path and points to the preferred 'builder spawn rail', giving an agent a clear basis for choosing this tool over siblings like attach_product_request_pr or claim_product_request_for_builder.

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?

It states the only allowed scenario explicitly ('Use this only when product team explicitly wants a tracking PR'), gives exclusions ('Do NOT use for questions or high/critical items that need design first'), and provides operational timing ('Call it on the first clear ask; the card is the yes — do not re-ask in chat'). This is unusually actionable.

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