duplicate_niagara_emitter

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

The description does not disclose behavioral traits beyond the basic action. With no annotations provided, the agent is left uninformed about side effects (e.g., whether the original is modified, naming conventions, or potential errors).

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 to the point, with a purpose line followed by an Args list. It is efficient, though the Args format could be slightly more structured (e.g., bullet points or clearer separation). No wasted words.

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?

While the description covers the basic purpose and parameters, it lacks context about prerequisites (e.g., system must be loaded), behavior (e.g., naming conflicts), and relationship to other tools. An output schema exists, so return values are assumed covered, but overall completeness is adequate but not thorough.

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?

Since the input schema has 0% description coverage, the description compensates by providing clear meanings for all three parameters: system_path, emitter_name, and new_name (optional). This adds significant value beyond the bare schema types.

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 'Duplicate an emitter within a Niagara System' and lists the key parameters. The verb 'duplicate' is specific and distinguishes from sibling tools like 'add_niagara_emitter' or 'remove_niagara_emitter', though no explicit comparison is made.

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 use this tool versus alternatives, nor are there prerequisites or context about the duplication process. The description only lists parameters without usage context.

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