Clone Change Event

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

Annotations already provide readOnlyHint=false, destructiveHint=false, idempotentHint=false. The description adds that it returns the newly created object with HTTP 201 and specifies required parameters. It does not contradict annotations, but the added behavioral context is moderate.

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 description is concise with front-loaded action and includes endpoint details. It is slightly verbose with the API version line but overall efficient.

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?

The description covers the return value (newly created object, HTTP 201) and mentions required parameters. For a clone tool with no output schema, it is fairly complete, though error conditions are not specified.

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% with descriptions for both parameters. The description reiterates required parameters and adds URL path vs query string info, but does not add significant meaning 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 clearly states it clones an existing Change Event, duplicates it, creates a copy, and returns the new object. It uses specific verb 'clones' and identifies the resource (Change Event). It distinguishes from create_change_event by being a clone operation.

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 says 'Use this to duplicate an existing Change Events as a new record,' indicating when to use it. However, it does not explicitly mention when not to use it or provide alternatives like create_change_event, but the purpose is clear enough.

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