github_repos_create_fork

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

No annotations present. Description implies a write operation but does not disclose behavioral traits such as permission requirements, where the fork is created (e.g., under authenticated user), or any side effects on the original repo.

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?

Extremely brief (two words) but under-specified. Conciseness is not beneficial when critical information is omitted. A longer description would be warranted.

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?

Given no annotations, no output schema, and a complex optional body parameter, the description is woefully incomplete. Agent lacks understanding of tool behavior, required inputs beyond owner/repo, and expected results.

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?

Input schema has 100% description coverage for parameters (owner, repo, body). However, description adds no additional meaning beyond the schema's simple labels. Baseline of 3 applies; no extra value provided.

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?

Description 'Create a fork' is a verb+resource but lacks specificity. It does not clarify that this is for repositories, possibly confusing with other fork operations like gists_fork or security_advisories_create_fork, which also exist in the sibling list.

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 guidance on when to use this tool versus alternatives. Sibling includes security_advisories_create_fork, but no distinction provided, leaving the agent without decision criteria.

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