duplicate_extension

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

Annotations indicate the tool modifies state (readOnlyHint=false) but is not destructive. The description adds no behavioral details beyond the name, such as whether the duplicate preserves configuration, requires permissions, or what happens to the original. Since annotations are present, the bar is lower, but the description still adds minimal value.

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, concise sentence without fluff. It efficiently conveys the core action. However, given the tool has four parameters, a slightly more detailed description could improve utility without sacrificing conciseness.

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 tool has no output schema, so the description should at least hint at the return value (e.g., new installation ID or success status). It currently provides no output information, making it incomplete for a mutating tool with no structured output documentation.

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 baseline is 3. The description does not elaborate on any parameter purpose or usage beyond what the schema already provides, such as clarifying that 'debug' enables diagnostic output. No added value.

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 the action ('duplicate') and the resource ('installed extension on a dashboard page'), making the tool's purpose immediately understandable. It distinguishes this tool from siblings like 'install_extension' or 'duplicate_field'.

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 provides no guidance on when to use this tool versus alternatives like 'install_extension' or 'create_extension'. It does not mention scenarios or constraints, leaving the agent without context for selection.

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