duplicate_record

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

No annotations provided, so description carries full burden. Successfully discloses key behaviors: creates independent copy (not linked), supports cross-database placement, and returns properties of new duplicate. Missing: permission requirements or idempotency notes.

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, zero waste. Front-loaded with core action, followed by critical distinction from siblings, then capabilities and return value. No redundancy with structured schema data.

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?

Appropriately complete for a 5-parameter mutation tool with no output schema. Compensates by describing return value ('Returns the properties...') and explaining cross-database capability. Minor gap: does not clarify that uuid/recordId/recordPath are alternative identification methods.

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 has 100% description coverage, establishing baseline 3. Description reinforces that 'Destination group UUID is required' (matching schema's required array) but does not add semantic context about mutual exclusivity of uuid vs recordId/recordPath identification methods.

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?

Clear verb-resource combination ('Duplicate a record') with explicit scope ('to any destination group'). Explicitly distinguishes from sibling tool 'replicate_record' by contrasting 'duplicates' with 'replicants' and explaining the independence property.

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?

Provides clear behavioral context to distinguish from 'replicate_record' (editing one does not affect the other). Implicitly guides selection by explaining the independence trait, though could be more explicit with 'Use this when you need independent copies vs. replicants for linked copies.'

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