get_niagara_renderer_properties

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

No annotations are provided, so description carries full burden. It discloses the tool returns current values and valid enum values. It implies read-only but does not mention error conditions or prerequisites. Adequate but not exhaustive.

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?

Description is well-structured with purpose, tips, examples, and parameter list. A bit lengthy but every sentence adds value. Front-loaded with main purpose.

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 the presence of an output schema, return values are not required. Description covers what the tool does, key parameters, and usage tips. Lacks error handling or edge cases, but overall complete for a read-only property getter.

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?

Input schema has 0% parameter descriptions. Description compensates with an Args section that explains each parameter, including filter usage and default for renderer_index. Adds meaning beyond type/required/default.

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 it gets editable renderer properties with current values and valid enum values. It distinguishes from siblings like set_niagara_renderer_property by focusing on reading properties.

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?

Provides explicit tips to use filter for token efficiency and lists common filters. Also explains property names can be used with set_niagara_renderer_property. Lacks explicit when-not-to-use vs alternatives like get_niagara_renderer_info.

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