Git for me! (checked live)

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

With no annotations, the description carries the full burden and does substantial work: it enumerates which conditions get flagged (no license, copyleft, archived, stale, little used, forks, mirrors), how from-memory picks are marked, and that unmatched finds are surfaced. It does not state read-only vs mutating nature, auth needs, or rate limits.

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 'Step 3 of 3: checks...' and free of filler, but the core is one very long sentence piling up flag after flag, which harms parseability. The conditional guidance is a clean second sentence.

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?

There is no output schema, so the description's account of what is returned (a report for the user, flags, from-memory marks, unmatched finds) is essential and present, and the nextAction loop is covered. Given the nested components schema and multi-step workflow, it is largely complete, though parameter-level and safety detail remain thin.

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 50%, so the schema partially documents the two parameters. The description clarifies the domain concepts ('picked repo', 'picks', 'marks picks the search didn't turn up as from memory') that map onto components/candidates, but adds no syntax or format detail for 'need' or 'components' beyond that.

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 action—checks each picked repo live on its forge—plus the downstream effects (drops missing, flags license/archived/stale/forks) and its place as 'Step 3 of 3'. The pipeline positioning distinguishes it from git_for_me_search, though the verb 'checks' is broad rather than precise.

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?

The 'Step 3 of 3' framing establishes ordering, and it explicitly states the conditional branch: 'If nextAction is SEARCH_FIRST or RECALL_REPLACEMENTS, do what its instructions say and call again.' No explicit when-not-to-use or named-sibling comparison, but the workflow context is clear.

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