get_repository

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

No annotations are provided, so the description carries the behavioral burden. 'Get' implies a read operation, but the description does not disclose required authentication, error behavior, rate limits, or any other operational characteristics beyond the action itself.

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, focused sentence with no filler. It front-loads the action and the resource, making the core purpose immediately clear.

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 read operation with an output schema and two obvious parameters, the description is mostly sufficient. The main gap is the complete lack of guidance about when to use it relative to repo-centric siblings like list_user_repos or search_repositories.

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 0%, so the description must compensate for undocumented parameters. It does not define what 'owner' and 'repo' mean, explain how they are validated, or describe the expected identifier format. The parameter names are self-evident only for someone already familiar with GitHub's API.

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 states a clear verb ('Get'), a specific resource ('a specific GitHub repository'), and implies precise object identification. This distinguishes it from sibling tools like search_repositories, which search broadly, or get_file_contents, which targets files.

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 phrase 'a specific GitHub repository' implies that the tool should be used when the owner and repo are already known, and it is not a search tool. However, the description does not explicitly explain when to choose this tool over siblings such as list_user_repos or search_repositories.

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