ue_list_uclass_methods

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

With no annotations, the description carries the behavioral burden itself. It discloses that this is a listing/introspection operation (no mutation implied), the filter_prefix behavior, and the exact JSON return shape including success, class_name, methods, and count. It does not describe failure behavior for invalid class names, but that is a minor gap for a read-only introspection tool.

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 one-line summary is front-loaded, followed by concise Args/Returns/Example sections. Every element earns its place, including the KB pointer and example call, with no redundant prose.

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 two-parameter introspection tool, the description is nearly complete: parameters, return format, example, and a KB reference. The only minor weakness is the slightly confusing suggestion that listing methods helps discover 'property names,' which could blur the boundary between methods and properties.

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 coverage is 0%, so the description must compensate, and it does. Both parameters are explained with concrete examples: class_name ('AssetToolsHelpers', 'EditorAssetLibrary') and filter_prefix ('import'). The default behavior is also clear from the schema default and the description's prefix-filter explanation.

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 opening sentence is a specific verb+resource statement: 'List callable methods on a UClass Python binding.' It is clear and distinct from property-oriented tools like ue_list_uclass_properties, though it does not name those siblings explicitly, so it falls just short of full differentiation.

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?

Provides concrete use cases: run before get_editor_property/set_editor_property to learn names, or before calling a method to confirm it exists. This gives clear context for when to invoke it, but does not state when not to use it or point to a named alternative.

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