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

Annotations declare this is a non-readonly, non-destructive, non-open-world, non-idempotent mutation. The description adds genuine context beyond that: the public-only constraint and the fact that a lineage link is retained. It omits duplicate-creation behavior implied by idempotentHint=false, keeping it just short of 5.

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?

Three tight sentences, front-loaded with the core action, then the usage rationale, then the exclusion. No filler or repetition.

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 single-parameter tool with annotations covering the safety profile and no output schema, the description supplies everything needed to decide and call correctly: the action, the prerequisite (public), and the fallback for private projects.

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 100% and the single parameter is already documented as 'The public project to fork.' The description only restates this as 'a PUBLIC project', adding no syntax, format, or ID conventions beyond the schema, so baseline 3 applies.

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?

Names a specific verb+resource+outcome: fork a public project into a new owned project while preserving lineage. It is clearly distinguishable from siblings like get_project, update_project, and share_project, which neither create nor copy.

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?

Explicitly states when to use it ('start from someone else's published model') and when not to ('only public projects can be remixed'), then routes the agent to the alternative workflow (read it and save the tree as a new project) for projects the user owns.

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