interchange_get_asset_import_data

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes further by disclosing the implementation path (LoadObject then GetAssetImportData), the ScriptExtract* calls, and crucially that a null result for legacy-factory imports is a normal `present:false` state rather than an error. That null-is-normal semantics is exactly the kind of context annotations cannot convey.

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 returns shape is useful and reasonably front-loaded, but the body is padded with header filenames, API macros (INTERCHANGEENGINE_API), and line-number citations (InterchangeAssetImportData.h/65) that add no decision value for an agent.

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?

With no output schema, the description compensates by spelling out the full return object and the null/present:false edge case, which is enough to call and interpret the tool. The remaining gap is the absence of any disambiguation from the similar `get_asset_import_data` sibling.

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?

Only one parameter, and the schema documents it at 100% coverage including both accepted path forms. The description adds no further meaning about asset_path, so the baseline of 3 applies.

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?

States a specific verb and resource: reads the UInterchangeAssetImportData of an asset, naming the exact engine type and manager call. However, it never distinguishes itself from the sibling `get_asset_import_data`, which reads a similarly-named concept, so an agent cannot tell the two apart from the description alone.

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 explicit when-to-use guidance, prerequisites, or named alternatives are given. The note that legacy-factory-imported assets return null is behavioral context rather than a routing rule, and the overlapping `get_asset_import_data` sibling is never mentioned.

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