get_abp_nodes

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

With no annotations, the description carries full burden for behavioral disclosure. It only states a read-only action ('Enumerate') but does not mention output format, error handling, or any prerequisites (e.g., path validity). It adds no behavioral traits beyond what is already inferable from the verb.

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 two sentences plus an args section. Every sentence serves a purpose—verb + resource, then parameter semantics. No filler, perfectly 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?

For a simple enumeration tool with two parameters and an existing output schema, the description covers the essentials. It lacks sibling differentiation and usage context, but the tool's relative simplicity and output schema reduce the need for extensive detail.

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 compensates well. It explains 'node_class' as a filter with a concrete example ('AnimGraphNode_BlendListByBool') and defines 'asset_path' as an Unreal asset path. This adds meaning beyond the raw schema fields.

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 uses a specific verb 'Enumerate' with a precise resource 'anim graph nodes in an AnimBlueprint', which clearly distinguishes it from siblings like get_abp_blend_nodes (which targets only blend nodes) and get_abp_graphs (which lists graphs).

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 is given on when to use this tool versus alternatives. It does not mention that this enumerates all nodes in an anim graph, nor does it point to sibling tools for filtered scenarios. The context of many sibling tools makes this ambiguity costly.

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