create_niagara_system

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

With no annotations, the description must disclose behavior. It says 'Create' but doesn't mention if overwriting occurs on existing path, what the output is, or any side effects. Template semantics are vague ('empty' vs path).

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 with a clear purpose sentence followed by parameter descriptions in Args format. No extraneous text. Front-loaded.

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?

Output schema exists, so return value documentation not required. However, given many sibling Niagara creation tools, the description lacks context for tool selection. Also, no mention of typical use cases.

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%, so description compensates well. asset_path explanation with example format adds meaning. template description clarifies options ('empty' or path). However, no further details on allowed templates.

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 'Create a new Niagara System asset.' with a specific verb and resource. It distinguishes from siblings like delete_niagara_system and list_niagara_systems. The example path adds clarity.

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 vs other creation tools (e.g., create_niagara_module_asset). No prerequisites or conditions mentioned. Template parameter described but no usage scenarios.

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