superops_assets_list

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

No annotations are provided, so the description should disclose behavioral traits like pagination, sorting, or result limits. While the schema includes cursor and max parameters, the description does not mention pagination behavior or how results are returned. This leaves gaps in understanding the tool's operation.

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 a single short sentence that is clear and to the point. It is front-loaded with the essential purpose. Minor improvement could include separate sentences for filters or pagination, but overall it is efficient.

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?

Given the tool has 5 parameters and no output schema or annotations, the description is too brief. It does not explain pagination (cursor, max), ordering, or the structure of returned results. For a list endpoint, these are important for proper use. The description is incomplete.

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 100%, so the description adds no new meaning beyond the schema itself. The statement 'Can filter by status, platform, or client' merely repeats what the schema already defines with enum values and descriptions. Baseline 3 applies as schema does the heavy lifting.

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 clearly states it lists assets/endpoints in SuperOps.ai RMM and mentions filtering by status, platform, or client. It effectively distinguishes from sibling tools like superops_assets_get (single asset) and superops_assets_patches/software (specific sublists).

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 usage for listing assets with filters but does not explicitly state when to use this tool versus alternatives like superops_assets_get for a specific asset or superops_assets_patches for patches. No exclusions or when-not guidance is provided.

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