LIST_DATA_ASSETS

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only listing but does not disclose pagination, result size limits, authorization requirements, or what happens when the connection parameters match nothing.

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?

A single tight sentence with the action and filter basis front-loaded and no wasted words. Its brevity is appropriate, though there is nothing else to front-load because the sentence contains so little.

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?

This is a four-required-parameter tool with no annotations and no output schema, meaning the description should explain the shape of the returned Presto tables and any filtering behavior. It provides neither, and also leaves ambiguity around whether all four connection parameters are mandatory.

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 all four parameters (container_id, container_type, presto_engine_id, presto_instance_crn) are already documented in the schema. The description only alludes to 'connection parameters' generally and adds no format, constraint, or relationship detail beyond the schema, which is the expected baseline.

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 states a specific verb (returns/list) and resource (Presto tables) plus the filtering basis (provided connection parameters), so the core action is unambiguous. However, it does not distinguish this tool from the sibling QUERY_DATA_ASSETS, so an agent cannot tell from the text alone which data-asset tool to pick.

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?

There is no guidance on when to call LIST_DATA_ASSETS versus QUERY_DATA_ASSETS, nor any mention of prerequisites such as having a valid Presto instance CRN or engine ID. The agent must infer usage conditions entirely from the name.

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