get_repo

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

No annotations are present, so the description carries the burden of disclosing behavior. 'Get' and 'detailed information' convey a read-only lookup, and the examples (stars, language) imply what fields the response contains. It does not mention auth, rate limits, or error behavior, but the output schema covers return details.

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 front-loaded with the core purpose, followed by a brief usage rule with examples and a compact Args section. Every sentence adds value, and the examples are well-chosen rather than redundant.

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 two-parameter read-only tool, the description covers purpose, usage, and parameter meaning. The presence of an output schema means return values need not be spelled out. It lacks explicit error-handling or authentication notes, but these are minor for a public GitHub lookup.

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 schema has 0% description coverage, so the Args section must compensate, and it does. It defines 'owner' as a GitHub username or organization, and 'repo' as the repository name (not the full URL), with several examples for each.

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 opening sentence, 'Get detailed information about a specific GitHub repository,' names a clear verb, object, and scope. The three example queries reinforce that the tool targets a single, known repository, distinguishing it from sibling tools like search_repos or list_issues.

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 explicitly says 'Use this when the user asks about a known repository' and gives concrete query examples. It does not list alternative tools or state when not to use it, so it stops short of full when/when-not guidance.

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