review_repository

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

With no annotations, the description must carry the behavioral disclosure burden. It communicates the core behavior—analyzing and generating a report with a numeric score—but does not clarify side effects, authentication/network requirements, or whether the report is returned directly or persisted somewhere.

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 a single, direct sentence that front-loads the action and the concrete output. There is no filler or redundant wording.

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 simple two-parameter tool, the core purpose is adequately stated, but the lack of an output schema and annotations leaves gaps around the report's structure and potential side effects. The absence of guidance versus review_all_repositories also weakens completeness.

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%, with both owner and repo parameters described, so the baseline is 3. The description itself adds no parameter-level details beyond what the schema already provides.

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 action (analyze), the resource (GitHub repository), and the output (quality report with a 0-100 score). The singular 'un repositorio' helps distinguish it from sibling review_all_repositories and other tools like generate_readme or clean_repository.

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 description implies usage for analyzing one specific GitHub repository, but it provides no explicit guidance about when to use this tool versus review_all_repositories or other sibling tools. No alternatives or exclusions are mentioned, leaving the agent to infer the selection criteria.

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