list_flexible_assets

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

With no annotations, the description carries the full behavioral burden. It discloses output_format options, default compact behavior, page numbering, max page_size, partial-match name filtering, and save_to_file's side effect of writing a temp file and returning its path. It stops short of stating read-only behavior or error handling, but core output and side-effect behavior are transparent.

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 organized as a one-line summary, an Args list, and a Returns line. Each entry adds non-redundant information, and the first sentence states the core purpose immediately. The length is justified by the need to document eight parameters absent from the schema.

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 list tool with eight optional parameters and no schema descriptions or annotations, the description covers filtering semantics, output formats, and return type well. The main missing context is how this tool relates to sibling list/search variants, which is a selection concern rather than an invocation blocker.

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%, so the description is the only documentation for all eight parameters. It defines each filter's meaning, notes partial matching for name, documents page numbering, caps page_size, enumerates output_format values, and explains save_to_file behavior. This fully compensates for the empty schema descriptions.

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 opens with 'List flexible asset instances,' a specific verb and resource. It clearly identifies this as the plural listing counterpart to get_flexible_asset and distinguishes from list_flexible_asset_types via 'instances,' though it does not explicitly name or contrast with those siblings.

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 guidance is given for when to use this tool instead of search_flexible_assets, get_organization_flexible_assets, or get_flexible_asset. The parameter list implies filtering use cases, but the agent must infer the boundary between 'list' and 'search' variants. This is a clear gap for a tool with many list/search siblings.

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