get_repository

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

Annotations are absent, so the description carries the full burden of behavioral disclosure. The word 'get' implies a read-only operation, but no further details are given—no mention of authentication, rate limits, return format, or whether the full repository object is returned. This is minimal and insufficient for a tool with zero annotation coverage.

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 sentence with no wasted words, so it is concise in length. However, it lacks substance—there is no key information to front-load because the content is a generic statement. It is appropriately sized but does not structure or prioritize any meaningful details.

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?

Given the tool's simplicity (2 required parameters, no output schema, no annotations), this description is severely incomplete. It does not explain what 'information' is returned, does not describe parameter semantics, and does not provide any operational context. An agent would have to guess or rely on external knowledge to call this tool correctly.

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, and the description does not mention the owner or repo parameters at all. It adds no meaning beyond the schema's type definitions. An agent must infer that owner is the GitHub owner and repo is the repository name, but there is no explicit guidance, leaving the parameters effectively undocumented.

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 a specific action ('Get information about a GitHub repository') with a clear resource. It is distinct from sibling tools (search_issues, list_pull_requests, search_repository_issues) which focus on issues/PRs, so the purpose is unambiguous. However, it does not explicitly differentiate itself from these siblings, and 'information' is vague, leaving what exactly is returned unspecified.

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 on when to use this tool versus alternatives. The description does not mention that this is for repository metadata, nor does it discuss when to use search_issues or list_pull_requests instead. The distinction is implied by the sibling names but not stated explicitly.

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