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

With no annotations, the description carries the full burden and does disclose meaningful behavior: the auth requirement, the requirement that the repo be within the installation, and three specific error modes including install_url for github_app_not_installed. It still leaves some read-only behavior implied by 'get' rather than stated, but it is substantially transparent about failure conditions.

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 definition is short and front-loaded: purpose first, then auth requirement, then binding/installation error cases. Each sentence carries relevant information, though the error cases are compressed into sentence fragments rather than a structured list.

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 single-repo metadata read with a documented output schema, the description covers the essential prerequisites and binding/installation failure modes. It could go further by naming the closest alternatives, but nothing critical is missing for correct invocation.

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 coverage is 100% and the single parameter is already documented as 'owner/repo the org's GitHub App already serves.' The description reinforces the binding constraint by explaining that a repo outside the installation returns github_repo_not_bound, but it adds no syntax or format detail beyond the schema. Baseline 3 is appropriate when the schema already does the heavy lifting.

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 names a specific verb/resource combination: 'Repository metadata for one connected repo.' This distinguishes it from the likely list sibling, but it does not explicitly name alternatives or clarify how it differs from github_repo_list or github_tree.

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 provides preconditions such as requiring memory:read and the repo being connected, but it does not say when to use this tool versus github_repo_list, github_tree, or other GitHub siblings. An agent must infer the selection criteria from the tool name alone.

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