superops_assets_list

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

No annotations are present, so the description carries the burden of behavioral disclosure; 'List' conveys a read-only operation and the filter sentence describes query behavior. However, it does not mention pagination/cursor behavior, result shape, or any operational details beyond the verb, leaving noticeable 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?

Two compact sentences with the primary action front-loaded and no filler. The filter list is expressed efficiently and adds immediate value without repeating schema details.

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?

Without an output schema or annotations, an agent must infer the return shape from 'List assets' and the pagination parameters in the schema. The description does not explicitly mention pagination, result limits, or how filters combine, so it is adequate but not fully complete for a list tool with cursor-based pagination.

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 the baseline is 3. The description echoes the filter parameters (status, platform, client) using friendly labels, but it adds no new semantic detail about max or cursor beyond what the schema already provides.

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 a specific verb 'List' and names the resource 'assets (endpoints)' in SuperOps.ai RMM. It clearly identifies this as the collection/list operation and distinguishes it from sibling tools like superops_assets_get, superops_assets_software, and superops_assets_patches.

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 implies the tool should be used to enumerate assets and shows what filters are available, but it does not explicitly state when to prefer this over sibling tools such as superops_assets_get or superops_assets_software. No exclusions or alternative routing are provided; usage context is inferred rather than spelled out.

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