Recommend repositories

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

With no annotations, the description carries the full burden and does well: it discloses the exact scoring model (momentum 40%, maintenance 25%, adoption incl. npm/PyPI downloads 25%, license 10%), so the agent understands the ranking is deterministic and transparent rather than opaque. It does not cover latency, rate limits, or empty-result behavior, but for a read-only recommendation tool the scoring disclosure is the materially important trait.

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 behavior and result shape in one dense sentence, followed by a short usage cue. Nothing is wasted, though the scoring-weight parenthetical makes the first sentence long enough to border on overloaded.

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?

With no output schema, the description does explain the return shape (ranked list, score breakdown, one-line verdicts), which is exactly what's needed. Its only meaningful omission is disambiguating itself from trending_repos and compare_repos, which an agent choosing among three repo tools would want.

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%, so baseline is 3. The description adds value for `need` by giving concrete examples ("python pdf parser", "react state management") that clarify phrasing, but says nothing about `limit` or `language` beyond the schema.

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?

Names a specific verb (recommend) and resource (open-source repositories) and describes the returned artifact precisely: repos ranked by a transparent 0–100 score with a one-line verdict each. Sibling differentiation is implicit rather than explicit — it never names compare_repos or trending_repos, but the 'ranked by score' framing separates it functionally.

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?

"Use before adding a dependency" gives a clear triggering context. It stops short of when-not-to-use guidance and never names the sibling tools as alternatives for related tasks (e.g. comparing two known candidates).

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