page_duplicate

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

The description only repeats the tool name and provides no additional behavioral details. With no annotations, the agent gets no insight into side effects, permissions, or the effect of the dryRun parameter.

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 very short but fails to be concise in a helpful way; it omits critical information and includes irrelevant text about Phase 2.

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?

With no output schema, no annotations, and 3 undocumented parameters, the description is severely inadequate. It provides no information about return values, side effects, or parameter formats.

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 0% and the description does not explain any parameter, leaving 'projectPath', 'pageName', and especially 'dryRun' ambiguous.

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 a page') and distinguishes from siblings like page_add or visual_duplicate. However, it lacks specificity about scope (e.g., within same project) and includes extraneous 'Planned for Phase 2'.

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?

No guidance on when to use this tool versus alternatives like page_add or page_rename. No exclusions or prerequisites are mentioned.

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