get_repository_info

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

With no annotations provided, the description must disclose behavioral context. It only states that metadata is fetched, implying a read operation, but doesn't mention whether authentication is required, how optional parameters behave, or any side effects (e.g., rate limits). This is a thin disclosure for a tool with no annotation support.

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 concise sentence that front-loads the action and enumerates the returned fields. Every word contributes value, with no redundant phrasing or filler.

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, but the description lacks essential context: it doesn't clarify the optional parameter relationship (e.g., whether both owner and repo are needed), what happens if both are null, or the exact return structure. Since there is no output schema, the description should provide more detail about the response, which it only partially does by listing fields.

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%, and the description entirely omits the 'repo' and 'owner' parameters. It adds no meaning beyond the property names themselves, which are self-explanatory but could benefit from clarifying how they combine (e.g., 'owner/repo' vs separate). The description fails to compensate for the lack of 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 uses a specific verb ('Fetch') and clearly identifies the resource ('repository metadata') with a list of concrete fields (description, default branch, language, topics). It distinguishes from siblings like get_readme and list_branches, though it doesn't explicitly state those exclusions.

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 implies use when repository metadata is needed but provides no explicit guidance on when to use this tool versus alternatives like get_readme or list_branches. There are no when/not-to-use conditions or prerequisite context.

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