get_repo

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

The description is consistent with the readOnlyHint=true annotation and confirms the operation is a read-only fetch. However, it adds little beyond that: it does not mention authentication requirements, failure behaviors, or what set of repository data is returned, though an output schema is present.

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 one short, front-loaded sentence with no filler. It states the action and the required identifying information efficiently.

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-string-parameter tool with an output schema and a read-only annotation, the description covers the basic purpose. However, it relies heavily on the agent already knowing GitHub owner/repo conventions and does not route the agent away from obvious sibling tools like list_repos or search_repos.

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 provides 0% parameter description coverage, so the description must compensate. Saying 'by owner and name' maps to the owner and repo parameters but largely restates them with synonyms and gives no format, constraint, or example for either value.

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 uses a specific verb ('Get') and resource ('repository'), and 'by owner and name' clarifies that this is a single-repository lookup. It is clearly distinguishable from sibling tools like list_repos or search_repos, though it does not explicitly name them.

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 intended usage is implied: use this when you need a specific repository by owner and name. There is no explicit guidance about when to prefer this over list_repos, search_repos, or get_file_content, and no when-not-to-use exclusions are provided.

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