Clone Folder View

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

Annotations show readOnlyHint=false, destructiveHint=false, so the tool is a mutation but not destructive. The description adds 'Duplicate' which implies creation of a new view. However, it doesn't disclose whether the source view is left unchanged, what happens if a view with the same name exists, or any authorization requirements. Acceptable for a straightforward copy operation.

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, clear sentence that immediately conveys the tool's purpose. It is efficiently worded with no unnecessary details, making it easy for an AI agent to parse.

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 an output schema present, return values are covered. The 5 parameters are all documented. However, missing context includes prerequisites (e.g., source folder must exist and contain the specified view), potential side effects (e.g., does cloning inherit all properties?), and constraints like the target folder needing to be different from source. Adequate but not comprehensive.

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 parameters are well-documented in the schema. The description does not add new information about parameter semantics beyond what the schema provides. Baseline score of 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?

The description clearly states the action ('Duplicate'), the resource ('existing folder view'), and the destination ('into a target folder'). It uniquely identifies the tool's function among siblings like clone_folder and clone_recorder, which operate on different entities.

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. For instance, it doesn't explain when to prefer cloning a view over creating a new one, or whether cloning a view duplicates its content, filters, or permissions. The description lacks usage context.

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