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

Annotations already declare readOnly=false and destructive=false, so the description is not the sole source of the safety profile, and it correctly corroborates a non-destructive write. It adds useful value by disclosing the return value ('Returns the new fork ID') despite no output schema, but says nothing about whether the fork is independent of, or affects, the source template.

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?

Two tight sentences, front-loaded with the action and followed by the result. No filler or redundancy.

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 3-parameter mutation tool with no output schema, the description covers the action and the return value, and annotations carry the safety profile. However, it omits fork independence from the source template and any overwrite/duplication behavior, which an agent would want before calling.

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%, so all three parameters (id, name, parameterOverrides) are already documented in the schema. The description repeats the 'parameter overrides' concept without adding format, merge semantics, or conflict-resolution details beyond the schema.

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 (fork) and resource (protocol template), plus the effect: creating a customized copy with parameter overrides. An agent can distinguish it from list-style siblings like get_protocol_forks, though it never explicitly contrasts with create_protocol or fork_dashboard.

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?

Usage is only implied by the phrase 'create your own version with parameter overrides' – there is no explicit when-to-use statement, no prerequisites, and no named alternative (e.g. create_protocol vs. fork_protocol). Adequate but leaves routing to inference.

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