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

Annotations already signal this is a mutating but non-destructive operation. The description adds useful behavior context by saying dates shift relative to the new start date, but it does not explicitly state that the original trip is left unchanged or what happens to entity relationships beyond a broad 'all its data' claim.

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 short sentences carry the core purpose and the key behavioral nuance. There is no filler, and the most important information is front-loaded.

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 an 8-parameter mutating tool with no output schema, the description is adequate but leaves gaps: it does not describe what a successful clone returns, whether the source trip remains untouched, or how the optional include flags relate to the 'all its data' claim. Schema and annotations fill some gaps but not these.

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 the parameters are already well documented. The description restates the date-shift concept already present in the startDate parameter and offers little additional semantic value 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?

The description uses a specific verb ('Clone/duplicate') with a clear object ('a trip') and scope ('with all its data'). This clearly distinguishes it from trip_create, trip_update, and other trip operations in the sibling list.

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 gives clear context: use this when duplicating an existing trip and its data. It does not explicitly name alternatives or exclusions, such as 'use trip_create for a blank trip', but the use case is unambiguous enough for an agent to route correctly.

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