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

Annotations already declare a non-destructive, non-idempotent write, so the bar is lower, and the description still adds substantive behavior: copies retain item text and sections, every item starts unchecked, copies are limited to 10 and stay on the same trip. What it omits is the response shape and whether the source must be non-empty.

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 sentences with no filler: action and scope first, then behavior of the copies, then required inputs. Every clause carries information an agent needs.

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?

There is no output schema, yet the description never indicates what is returned (e.g., new checklist IDs or titles), which is the one thing an agent needs to chain follow-up calls. Everything else for correct invocation is present given the full schema coverage.

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% and both parameters are documented there, including the 1-10 range and 200-character limit. The description mainly restates the schema (segment ID from trip_details, one title per copy, max 10) rather than adding new semantics, so baseline 3 is appropriate.

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 (duplicate) and resource (checklist), plus the outcome: one or more new checklists on the same trip. This is clearly distinct from creation siblings like segment_create or batch_segment_create, though it never names an alternative explicitly, which keeps it at a 4 rather than a 5.

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?

It gives the prerequisite that source_note_id comes from trip_details, which is real usage context, but offers no when-to-use vs when-not guidance and never points to a sibling tool for adjacent operations. Usage is implied rather than stated.

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