_get_repository

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

There are no annotations, so the description carries the burden of disclosing behavior. 'Get' implies a read operation, but the description does not explicitly state read-only semantics, authentication requirements, or any side effects; it also leaves 'detailed information' unspecified. This is a minimal level of transparency.

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 short and front-loaded, with the main action in the first sentence. The Args section is somewhat redundant with the schema but adds a small clarification; overall it is appropriately sized.

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?

The tool is simple and an output schema exists, so return values do not need to be documented. Still, the description omits usage context (when to choose this over listing/searching repositories) and any behavioral caveats, leaving an agent to infer those from the name and siblings.

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 the undocumented parameters. However, 'owner: Repository owner' and 'repo: Repository name' merely restate the parameter names and add almost no functional detail about format, scope, or constraints. The description fails to fully compensate for the missing schema descriptions.

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') and resource ('detailed information about a repository'), so an agent can identify the operation. However, it does not differentiate from sibling read tools such as _list_repositories or _get_organization beyond the resource name, which is fairly self-evident.

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?

No guidance is provided for when to use this tool instead of a sibling such as _list_repositories, _get_organization, or update_repository. There are no prerequisites or exclusion criteria; usage is only implied by the generic 'get repository' phrasing.

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