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

Annotations only declare the generic profile (not read-only, open world, not idempotent, not destructive). The description adds real behavior: the copy is a new resource placed in the source workspace versus the caller's account depending on write access, and that a 'why' is mandatory for workspace writes but not for copies landing in your own account. It does not spell out error behavior for unreadable sources or that repeated calls create separate copies.

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 key verb is front-loaded and there is no filler, but the first sentence is a dense run-on that packs id source, endpoint, and three destination cases into one stretch, with nested parentheses ('(with why)', '(no why)'). It is compact rather than readable; the destination rules could be one short list instead of embedded clauses.

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?

An output schema exists, so return values need not be described, and the annotations cover the safety profile. Given a fork tool whose real complexity is destination and permission branching, the description covers the placement cases and the 'why' requirement; only edge cases (unreadable source errors, table rejection behavior) are left implicit.

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%, so artifactId, versionId, folder, team, title and why are all documented in the schema, which sets the baseline at 3. The description mostly echoes the folder id-or-slug resolution and the artifactId = current version semantics already in the schema, adding only the conditional framing of when 'why' is needed.

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?

States a specific verb and resource: forks a readable non-table artifact into a copy, mapping to POST /v0/forks, and explicitly excludes table artifacts and names the two id sources (artifactId vs versionId). It is distinguishable from siblings like artifact_move, artifact_upload and artifact_get, though the purpose sentence is overloaded with placement conditionals that belong to usage guidance.

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?

Gives explicit conditional branches for the copy's destination: source workspace when writable (with why), own account standalone for public-link-only reads, standalone for standalone sources, plus folder slug resolution order (copy workspace, else team, else personal). It never states when to fork rather than upload or read-then-create, so it is strong context but not full alternative routing.

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