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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true. The description adds genuinely non-redundant behavior: the result is private to you until shared, it runs without asking (no confirmation prompt), and it requires a Cotlet API key with app access. These are real operational facts an agent otherwise couldn't infer.

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?

Purpose is front-loaded, which is good, but sentence two ('Creates a copy of the deck in your library') largely restates sentence one ('Copy any presentation in your library'), and the trailing auth-key note is tacked on rather than integrated.

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?

No output schema exists, and the description compensates by stating the return value (the copy's ID). It covers auth requirements and the privacy/auto-approve behavior. A mutation tool with a two-param schema is adequately covered, with only minor room for more detail on what 'private' entails.

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 both parameters (presentation_id and optional title with its default) are already documented. The description adds only marginal semantics by noting the tool returns the new ID; 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 (Copy/Duplicate) and resource (presentation in your library), and anchors it to a familiar UI action ('as the Duplicate menu item does'). It does not differentiate from any sibling, but no sibling overlaps this operation, so the purpose is unambiguous.

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?

Implies usage context ('Copy any presentation in your library') and notes the copy is private until shared, which hints at why/when you'd duplicate. There is no explicit when-not-use guidance or named alternative, so it stays at implied usage rather than active routing.

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