place_bp_anim_notify

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

No annotations are provided, so the description carries the full behavioral burden. It reveals what the placed notify can do, but never states whether placement mutates/saves the animation asset, whether it overwrites an existing notify at that time, permission prerequisites, or idempotency. For a mutation tool with zero annotation coverage, key operational traits are missing.

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?

Front-loaded statement of what the tool does, followed by a useful sibling contrast, then an Args block. Every section earns its place with little padding; the only minor redundancy is restating the example path inline in both prose and the Args list.

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?

An output schema exists, so return values need not be explained. Parameters are well covered, but for a mutation tool with no annotations the description leaves side effects (asset save, existing-notify handling) unspecified, which is a meaningful gap for an agent deciding how to invoke it safely.

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 the description must compensate — and it does: all four parameters are documented with concrete example paths, the units for time (seconds), and the default value for notify_name. It adds real meaning beyond the bare types in the schema, though it doesn't specify path format constraints or valid ranges.

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?

Specific verb (place) + resource (Blueprint-based AnimNotify on an animation) + scope (at a specific time). It explicitly distinguishes itself from the sibling place_anim_notify by naming what that tool creates (engine AnimNotify_PlaySound) versus what this one places. An agent can route between the two without opening either schema.

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 names the alternative (place_anim_notify) and the condition that selects it — use this one when you need BP notify classes that perform surface detection, line traces, and material-based sound selection, the 'Lyra footstep pattern'. This is an explicit when-to-use-this-instead-of-that statement.

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