add_niagara_map_set_pin

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

No annotations exist; the description only states the action without disclosing side effects, modifications to the asset, or requirements. The behavioral impact (e.g., modifying the scratch pad) is not stated.

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 front-loads the main action. The Args section adds some length but remains efficient. Every sentence contributes, though the reference to add_niagara_map_get_pin could be a minor distraction.

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?

Despite having an output schema to cover return values, the description lacks context on prerequisites, error cases (e.g., missing MapSet node), and interaction with other Niagara tools. Not sufficient for a graph-editing tool with many siblings.

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%. The Args section lists parameters and gives brief descriptions, but parameter_type references another tool for details, and the descriptions are minimal. Insufficient to fully compensate for the lack of schema documentation.

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 adds a typed input pin to the first ParameterMapSet node in a scratch pad graph, with a reference to the UI action, distinguishing it from siblings like add_niagara_map_get_pin.

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?

Implies usage through the mention of mirroring the '+' click, but no explicit when-to-use, when-not-to-use, or comparison to alternatives like add_niagara_node_pin. No prerequisites or context provided.

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