project_clone

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It reveals nothing beyond the verb 'Clone'—no mention of whether the source is copied, whether target_path must not already exist, permissions, side effects, or what the tool returns. This is effectively a restatement of the name.

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 short and free of fluff, but it is under-specified rather than effectively concise. There is no structured content to front-load, and the brevity comes at the cost of nearly all useful 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?

Given a 2-parameter clone operation with no annotations and no output schema, this description is severely incomplete. It omits return values, failure modes, overwrite behavior, and the relationship to project_create, so an agent cannot reliably invoke or handle results based on this description alone.

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 0%, and the tool description adds no parameter-level meaning. The names project_id and target_path are somewhat self-explanatory, but the agent receives no guidance on expected formats, path requirements, or relationships between the two parameters.

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 uses the verb 'Clone' and resource 'project', conveying a duplication operation. However, it essentially restates the tool name and does nothing to distinguish it from sibling tools like project_create or open_project, or to clarify that it duplicates an existing project into a target path.

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?

There is no guidance on when to use project_clone versus alternatives such as project_create, open_project, or import_xml. No prerequisites, exclusions, or context are provided, leaving the agent to infer proper usage entirely from the tool name and parameters.

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