list_enums

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond that: it enumerates currently loaded UEnum types, includes both native and user-defined/Blueprint enums, and documents the shape of the returned data including nested enum entries.

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?

Two sentences with no filler. The purpose and scope are front-loaded, and the return shape is provided compactly without repeating schema information. Every sentence earns its place.

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 read-only enumeration tool, the definition is complete: purpose, scope, filters, and return structure are all covered. Annotations supply the safety profile, and the schema documents every parameter, so there is no missing information needed to call the tool correctly.

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 100%, so the parameter descriptions already document name_pattern, module_filter, and the pattern alias in detail. The description only restates that filtering by module or name substring is optional, adding no syntax or behavioral detail beyond the schema. Baseline 3 is appropriate.

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') and resource ('loaded UEnum types (native + user-defined/Blueprint)') with a clear scope ('optionally filtered by module or name substring'). This distinguishes it from single-enum inspection tools like get_enum_info and enum-editing tools like create_enum or add_enum_entry, so an agent can select it without opening the 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 gives no explicit guidance on when to use this tool versus alternatives. It only states that filters are optional, and it never names a sibling or a scenario where another tool would be more appropriate. An agent is left to infer that this is the bulk enumeration tool from its name alone.

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