github_ensure_fork

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

With no annotations provided, the description fully carries the burden of disclosure. It clearly states the mutating side effect (creates a fork), idempotency (only if not exists), returns metadata (slug, clone URLs, newly created flag), and the allowlist constraint. This exceeds basic behavioral transparency.

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 concise and front-loaded: the first sentence states the core purpose, followed by two sentences that clarify behavior, return values, and a prerequisite. Every sentence earns its place with no redundant language.

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 the tool has one parameter and an output schema, the description is complete. It covers the action, side effects, what is returned, and a critical precondition (allowlist). There is no missing information that would hinder an agent from using the tool correctly.

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 input schema only defines repo_slug as a string with zero description coverage. The description adds meaning by identifying it as the 'upstream repository' and imposing an allowlist constraint. However, it does not explicitly specify the expected format (e.g., owner/repo), leaving some ambiguity.

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 clearly states the tool's purpose with a specific verb ('Ensure') and resource ('fork for the given upstream repository'). It distinguishes itself from siblings like repo_clone by focusing on fork creation rather than cloning, and clarifies it creates under the authenticated user's account.

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 provides clear context: when a fork must exist for an upstream repository, this tool ensures it. It also mentions an allowlist prerequisite. However, it does not explicitly compare with alternatives (e.g., repo_clone) or state when not to use it, so it lacks exclusions.

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