fork_repo

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It communicates the core effect — a repository is copied into the authenticated user's account — but it does not disclose details such as whether the source repository remains unchanged, whether an existing fork is returned, or whether the operation can be asynchronous.

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. It front-loads the verb and resource, and the destination clause adds useful context without verbosity.

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 tool with two required string parameters and an output schema, the description is minimally sufficient. It names the destination and core action, but with no annotations and no mention of edge cases like already-forked repos or ownership restrictions, an agent is left to infer some behavioral details.

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 explain the roles of 'owner' and 'repo'. The parameter names are conventional and inferable from the tool name, but the description adds no explicit semantic meaning beyond what the schema already shows.

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 ('Fork') with a specific resource ('a repository') and names the destination ('into the authenticated user's account'). This clearly distinguishes the tool from sibling creation, deletion, and file-management tools even without naming alternatives.

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 gives a clear context for when to use the tool: forking a repository into the authenticated user's account. However, it does not explicitly state when not to use it or mention any alternative tools, leaving usage guidance implied rather than explicit.

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