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

With no annotations, the description carries the full transparency burden. It discloses key behavioral traits: manual-only invocation, the approval flow (first use may require manager approval, from-now-on vs just-once behavior), and the reason for the change ('polluted ship-seat'). It does not describe return values or exact side effects, but the provided context is strong for a write-tier tool.

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 concise and front-loaded with the critical 'MANUAL ONLY' caveat and the core action. It conveys essential usage rules and approval nuances in two short paragraphs without redundancy. Every sentence contributes to invocation correctness.

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 tool with 3 parameters and no output schema, the description provides sufficient context: purpose, manual-only restriction, approval workflow, exclusions, and preferred alternative. It lacks explicit return-value information, but that is not mandatory given the schema's parameter descriptions and the tool's clear output (a draft PR shell). Overall, it is nearly complete for an agent to invoke 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 each parameter includes a clear description in the schema. The tool description does not add meaning beyond the schema; it only reinforces the overall purpose. With full schema coverage, a 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 clearly states the tool's purpose with a specific verb and resource: 'open a draft GitHub PR shell for an approved FreedomOS product request.' It also differentiates from siblings by noting 'Approve no longer auto-opens a ticket PR' and directing to 'Prefer the builder spawn rail,' making the tool's unique role unmistakable.

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?

Explicit when-to-use and when-not-to-use guidance is provided: 'Use this only when product team explicitly wants a tracking PR' and 'Do NOT use for questions or high/critical items that need design first.' It also flags the preferred alternative ('builder spawn rail'), giving the agent clear decision criteria.

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