list_assets

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

No annotations are provided, so the description carries the burden. It discloses that the tool lists assets and returns a markdown-formatted list, which is useful. However, it does not mention authentication requirements, sorting, pagination, or potential errors, leaving some behavioral transparency gaps.

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 reasonably compact but redundant: the first sentence 'List all assets in the system.' is repeated almost verbatim by 'This tool lists all assets in the system...' This duplication could be removed to improve clarity without losing information.

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 list tool with two optional parameters and an output schema, the description is mostly complete. It explains the operation, filters, and return format. It could mention combined filter behavior or result ordering, but those are minor gaps for this complexity level.

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%, but the description compensates by explaining both parameters: 'Optional type to filter assets' and 'Optional classification to filter assets.' This adds meaning beyond the schema's bare string/null definitions, though it does not provide possible values or examples.

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 uses a specific verb and resource: 'List all assets in the system.' It clearly distinguishes from sibling tools like list_components, list_data_stores, and list_flows by naming the exact resource (assets). The optional filters further clarify scope.

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 states the tool can be optionally filtered by type or classification, giving implied context for when to use it. However, it does not explicitly mention alternatives or conditions for when not to use it, unlike examples that name sibling tools.

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