fork_project

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action is 'Fork', implying a write operation that creates a copy, but lacks details on permissions required, rate limits, whether it's idempotent, or what happens on failure. This leaves significant gaps for a mutation tool.

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 front-loaded with the core purpose in the first sentence, followed by structured Args and Returns sections. It avoids unnecessary words, but the Args/Returns formatting could be more integrated into natural language for better flow.

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 a mutation tool with no annotations, 2 parameters (0% schema coverage), and an output schema exists, the description is minimally adequate. It covers the basic action and parameters but lacks behavioral context like error handling or permissions, which is important for a tool that modifies data.

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 description coverage is 0%, so the description must compensate. It lists 'project' and 'namespace' with brief explanations ('Project name to fork', 'Project namespace') and a default for namespace, adding basic meaning. However, it doesn't clarify format (e.g., naming conventions) or constraints, leaving parameters partially documented.

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 action ('Fork') and resource ('Pagure project') with the destination 'to your namespace', making the purpose evident. However, it doesn't explicitly differentiate this tool from sibling tools like 'list_projects' or 'get_project_info', which are read-only operations, so it misses full sibling distinction.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing permissions or an existing project), compare to siblings like 'merge_pull_request' for related workflows, or specify scenarios where forking is appropriate versus other operations.

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