複製

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

Annotates only with title and openWorldHint=false, so description must carry behavioral load. It reveals deep copy, async processing at frame boundaries, synchronous return of real data (entityId, name, sceneGeneration). No contradiction with annotations.

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?

Concise two-sentence description, front-loaded with action and specification, no redundant 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?

Covers core operations, identification, processing timing, and return value. With an output schema likely present, return details suffice. Does not mention error cases (e.g., missing entity) but acceptable for a duplicate tool.

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 has 100% coverage with descriptions for both 'name' and 'entity' parameters. Description adds the value of exclusivity (either id or name) and links them to the duplication purpose, slightly enhancing semantics.

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?

Description clearly states it deeply duplicates an entity with children, specifying two identification methods (entity id or name). No sibling tool duplicates entities, making its purpose distinct.

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?

Tells when to use (to duplicate an entity with children) but does not explicitly state when not to use or mention prerequisites. Context is clear but lacks exclusions.

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