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

Adds substantial context beyond the annotations: naming fallback chain '(copy)', '(copy 2)', quota enforcement (templates_limit against active templates, rate_limited with details.code templates_daily_limit and details.retryAt for new templates in 24h), name_taken collision behavior, not_found for deleted/foreign templates, and the fact that already-rendered emails stay attached to the original. The description is consistent with destructiveHint=false and idempotentHint=false.

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?

Front-loaded with the core action, then defaults, then failure modes in a logical order with no filler sentences. It is dense — the middle sentence packs quotas, rate limits, and name collisions together — but every clause carries information.

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 a two-parameter mutation tool with no output schema, the description supplies everything an agent needs: what is copied, default naming with collision escalation, all failure codes with their trigger conditions, and an explicit statement of the return payload (new template, unusedTags, warnings, source).

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%, so the bar is met by baseline alone; the description goes further by explaining the naming sequence beyond what the schema states (schema only mentions '(copy)', description adds '(copy 2)' and onward) and tying templateId provenance to lnkdrp_list_email_templates. It does not elaborate on the 24-hex pattern, but the schema covers that.

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 and resource ('Copies an active or archived email template ... into a new active template') and enumerates exactly which fields carry over (name, description, format, align, subject, body, tags). This clearly separates it from lnkdrp_create_email_template (which builds from scratch) and from update tools, without needing to open the schema.

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 implies the appropriate situation (you have an existing template you want a working copy of, active or archived) and warns about the workspace cap and daily limit. However it never explicitly contrasts itself with lnkdrp_create_email_template or states when duplication is preferable to creating fresh, so the agent must infer that choice.

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