sdcloud_list_flow_based_antivirus_profiles

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

No annotations are provided, so the description must disclose behavior. It implies a read-only operation but does not explicitly state safety (no destructive effects), authentication needs, rate limits, or pagination behavior (e.g., default size). The description is too minimal to offer meaningful transparency beyond the operation type.

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 sentence that immediately starts with the verb 'List' and efficiently covers the resource and optional features. No redundant text; every word contributes to the purpose.

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?

There is no output schema, so the description should clarify the return format (e.g., list of profiles with fields, pagination metadata). It only says 'profile objects' without specifying structure. Combined with missing behavioral details, the description is insufficient for an agent to fully understand the tool's behavior and output.

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?

The input schema has 100% coverage with descriptions for all 5 parameters. The tool description summarizes them as 'pagination, filtering, and sorting' but adds no additional detail or examples. Since the schema already documents each parameter, the description adds limited semantic value beyond grouping the features.

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 'List flow-based antivirus profile objects', specifying the exact resource type and action. It distinguishes from sibling tools like sdcloud_list_anti_virus_profiles (non-flow-based) and the create/get/update/delete variants for the same object.

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 mentions optional pagination, filtering, and sorting, giving some usage context. However, it does not compare with alternative tools like sdcloud_get_flow_based_antivirus_profile for single-object retrieval, nor does it specify when not to use this tool. Basic guidance is provided but no exclusions or broader context.

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