导入工程目录内的文件

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

Annotations already state destructiveHint=true and readOnlyHint=false, so the agent knows this is a mutating, destructive operation. However, the description adds no behavioral context beyond what annotations supply—nothing about overwriting, path semantics, or side effects—so it fails to enrich the warning.

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, but it is a pure restatement of the title and does not earn its place. Conciseness is only valuable when the included sentences carry information; here the single sentence is empty.

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?

For a tool with 6 parameters, nested objects, a destructive annotation, and no output schema, the description provides virtually no operational context. An agent would not know import path semantics, error conditions, or expected effects.

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%, meaning the description must fully compensate for missing parameter documentation. The description says nothing about sourcePath, targetUrl, or how they relate to the project, leaving the two required parameters semantically black boxes.

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?

No guidance is provided on when to choose this tool over sibling tools. With 34 siblings performing overlapping asset and project operations, an agent would have no way to route to this tool correctly.

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