github_security_advisories_create_fork

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

With no annotations, the description must disclose behavioral traits. It states 'temporary private fork' but does not explain what 'temporary' entails (e.g., deletion after advisory closure), auth requirements, or side effects. This is insufficient.

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 single-sentence description is concise and front-loaded. It avoids redundancy but could be slightly expanded without losing conciseness. Still, it earns its place.

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 three parameters and no output schema, the description lacks context about how the temporary fork relates to security advisories, what happens after creation, and prerequisites. Incomplete for a meaningful tool invocation.

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?

Schema coverage is 100% but parameter descriptions are just names (owner, repo, ghsa_id). The description adds no extra meaning. Baseline 3 is appropriate as the schema covers the basic structure but lacks deeper semantics.

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 'Create a temporary private fork' uses a specific verb ('Create') and resource ('temporary private fork'). It clearly distinguishes from sibling tool 'github_repos_create_fork' which creates a regular fork. The purpose is unambiguous.

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 is provided on when to use this tool versus alternatives like 'github_repos_create_fork'. The description does not mention the context of security advisories or any conditions for use.

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