list_data_asset_classes

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

With no annotations, the description carries full burden. It accurately describes a read-only listing operation and details the returned data. However, it does not mention any behavioral traits like editor state prerequisites or performance considerations.

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 concise: two sentences that cover purpose and output without any redundancy or fluff.

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, the description omits input parameter explanations. For a tool with two optional parameters, the lack of parameter documentation makes it incomplete for proper usage.

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% and the description does not explain the 'filter' or 'include_abstract' parameters. Users cannot know how to use these parameters effectively without additional context.

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 the tool's action: list all UDataAsset subclasses. It specifies the exact return fields (name, class path, parent class, UPrimaryDataAsset flag, editable properties). This distinguishes it from sibling tools like list_data_assets (which lists instances) and search_parent_classes (which searches class hierarchies).

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 does not explicitly state when to use this tool or provide usage context. It implies that it lists class definitions, contrasting with list_data_assets for instances, but offers no direct guidance on filter or include_abstract parameters.

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