Duplicate an item with its assets + viz profiles (admin/editor on the project).

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

Annotations indicate this tool is not read-only (readOnlyHint=false) and not destructive (destructiveHint=false), but the description adds minimal behavioral context beyond the title. It does not disclose rate limits, error handling, or what happens if the new name already exists. The role requirement is useful but insufficient.

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 a single sentence that mirrors the title, which is concise but borderline tautological. It lacks structure or front-loading of key information, though it has no wasted words.

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?

Given the complexity (5 parameters, 1 required) and low schema coverage, the description should provide more context about the duplication behavior, default naming, and return value. Although an output schema exists, the description does not mention it or provide any additional completeness.

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 only 20% (only 'new_name' has a description). The tool description does not elaborate on any parameters, leaving most (especially x-api-key, target_collection_id, target_project_id) unexplained. The description fails to compensate for the low schema coverage.

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?

Tautological: description restates name/title.

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 tool is for copying items, but provides no explicit guidance on when to use it versus alternatives (e.g., items.create), nor any prerequisites or conditions. The role requirement is mentioned but not expanded.

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