fork_repository

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

With no annotations, the description carries the full burden and discloses almost nothing behavioral: no note that GitHub forks are asynchronous, no permission/auth requirements, no statement about whether an existing fork is returned or duplicated, and no indication of what 'active repository' resolves to.

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?

One sentence, zero waste, front-loaded with the action and immediately followed by the scoping qualifier. Nothing is padded or repeated from structured fields.

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 no-annotation, no-output-schema mutation tool, the description should cover side effects and async/duplicate semantics; it covers none of them. An agent knows what to call but not what to expect back or how the operation behaves.

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 single optional parameter has 0% schema coverage with no description, so the description is the only source of meaning. It does establish that 'organization' is a destination alternative to the authenticated user (implying user-default when omitted), which is genuine added value, but it gives no format, naming, or conflict behavior for that string.

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?

States a specific verb+resource ('Create a fork') scoped to 'the active repository', which an agent can distinguish from create_repository (new repo) without opening schemas. It stops short of explicitly naming that sibling, so differentiation is inferred rather than stated.

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 only guidance is where the fork lands (user vs. organization), which is parameter behavior rather than when-to-use. There is no statement of prerequisites, when to prefer this over create_repository, or what happens if a fork already exists.

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