get_repository

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'metadata and permissions' which indicates read-only access, but doesn't disclose return format details, pagination, or whether permissions info requires authenticated context. The phrase 'metadata and permissions' hints at read-only behavior but is not explicit about safety profile compared to siblings.

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?

A single, focused sentence with zero wasted words. It front-loads the verb and resource, and the token count is minimal while still conveying the tool's primary function.

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 has an output schema (which provides return value details) and only 1 required parameter, so the complexity is moderate. The description adequately names what is retrieved (metadata and permissions) but is thin on usage context and parameter guidance. For a relatively simple metadata-fetching tool, this is borderline adequate but could benefit from clarifying when to use vs inspect_local_repository.

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, but it doesn't explain either parameter. 'repo' is a string (likely repository identifier) and 'owner' defaults to empty (suggesting optional override), but neither purpose is clarified in the description. The description makes no reference to what repo/owner mean or how they relate, though the 'repository metadata' wording implies repo identifies the target.

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 ('Gets') and resource ('repository'), indicating this fetches repository metadata and permissions. It distinguishes from siblings like inspect_local_repository (local) and list branches/list_pull_requests (different resources), though it doesn't explicitly differentiate from get_collaborator_permission which is more narrowly permission-specific.

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 explicit when-to-use or when-not-to-use guidance is provided. The description doesn't mention that this is a read-only lookup appropriate for fetching repo metadata, nor does it contrast with alternatives like inspect_local_repository for local checking or get_collaborator_permission for targeted permission queries. Usage context is entirely implied.

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