evaluate_repo

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

No annotations exist, so the description carries the full burden. It usefully discloses the scoring model (popularity, momentum, maintenance, trust), the numeric range, and the verdict taxonomy, but says nothing about auth requirements, rate limits, latency, or how a repo that cannot be fetched is handled.

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?

A single dense sentence, front-loaded with the verb and resource, followed by the scoring dimensions and output categories. Every clause carries information; no filler.

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 steps in to describe the return payload - a 0-100 score across four named dimensions plus a four-level verdict - which is what an agent needs to interpret results. Error handling for malformed or missing repos is the only notable omission.

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?

The only parameter, repo, is fully documented in the schema ('owner/name' format or GitHub URL), which matches the description's scope but adds no syntax or format detail beyond it. Baseline 3 applies when the schema already covers the parameter.

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 verb (score) and resource (a single GitHub repository), plus the output scale (0-100), the scoring dimensions, and the verdict categories. 'Single' quietly distinguishes it from compare_alternatives, but the description never names the siblings explicitly.

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?

Usage is only implied: scoring one repo suggests this is for evaluating an individual candidate rather than searching (search_oss) or comparing options (compare_alternatives). No explicit when-to-use, when-not-to-use, or named alternatives are given.

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