list_repos

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

No annotations are present, so the description carries the full burden. It does disclose the operational scope (only public repos), the resource owner (the GitHub account), and the returned content (names and descriptions). However, it does not mention authentication requirements, pagination, rate limits, or ordering, which are relevant for a listing endpoint.

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, focused sentence with no filler or redundant information. It front-loads the action and resource, making it easy for an agent to understand the tool quickly.

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 parameterless list tool with an output schema and simple sibling context, the description is largely complete. It states the scope, subject, and included fields. It could slightly improve by noting that this is a read-only operation and whether the public-repo scope is the only intended use case.

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 tool has zero parameters and the schema description coverage is 100%, so there are no parameters to document. The description adds meaningful context about what the result will include, which is sufficient for a parameterless tool.

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 specific action ('가져옵니다' fetches) and a specific resource: all public repositories in the user's GitHub account, with names and descriptions. This clearly differentiates the tool from siblings like search_repos, which searches across repositories rather than listing the account's own public repos.

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 the tool is for listing the authenticated user's public repositories, but it does not explicitly state when to prefer this over search_repos or get_readme. There is no exclusionary guidance or mention of alternatives, so usage context is only implied rather than directed.

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