implement_approved_pins

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

No annotations provided, so description carries full burden. It describes the output structure and usage workflow. It does not mention side effects, auth, or rate limits, but as a retrieval tool this is adequate.

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 four sentences, front-loading purpose. Some redundancy in explaining workflow, but concise overall and well-structured.

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?

Given no output schema, description explains output shape (packets with CSS selectors, threads, branch name) and how to use it. Missing error cases or detailed return format, but sufficient for this tool.

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 100% with one optional parameter (projectId). Description adds minimal meaning beyond schema; it repeats the filtering behavior but does not enrich parameter semantics significantly.

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 returns stakeholder-approved pins grouped into implementation packets, specifying verb 'returns' and resource 'approved pins'. It distinguishes from sibling tools like get_implementation_packet and claim_pin by indicating it is the first step.

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?

Explicitly says 'CALL THIS FIRST when approved pins exist' and provides a workflow: implement_approved_pins → claim_pin → code change → fix_and_resolve. This guides when to use it vs alternatives.

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