add_niagara_event_handler

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It describes parameters but lacks details on side effects, prerequisites (e.g., existing system/emitters), error conditions, or return values. Critical for a mutation tool with 7 parameters and an output schema.

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 brief: a single sentence for purpose and a bullet list for arguments. It is front-loaded with the main action and avoids unnecessary words. Every line adds value.

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?

The description covers purpose and parameters adequately, but given the complexity (7 params, mutation, output schema), it lacks prerequisites, return value explanation, and error handling. Some behavioral context is missing, making it less complete for an AI agent.

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?

The input schema has 0% description coverage, so the description must fully explain parameters. It does so thoroughly, listing all 7 parameters with context (e.g., event name examples, execution mode meanings, default values). This adds significant meaning beyond the bare schema.

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 the verb 'Add', the resource 'event handler', and the target 'emitter', with the purpose of responding to events from a source emitter. This distinguishes it from sibling tools like add_niagara_emitter or add_niagara_module.

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?

The description implies usage for adding event handlers to emitters but does not explicitly state when to use this tool versus alternatives (e.g., modifying handlers via other tools) or when not to use it. No prerequisites or exclusions are mentioned.

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