acunetix_list_scan_profiles

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It mentions the HTTP GET method, implying a read-only operation, and provides the endpoint. However, it does not cover authentication needs, pagination, or any side effects, which are relevant for a complete understanding.

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 entire description is a single, compact Chinese sentence that packs both the endpoint and the usage purpose. Every element earns its place, with no redundancy or extraneous 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 zero-parameter list operation with no output schema, the description provides the API endpoint and the intended usage context. It does not describe the return structure, but that is easily inferred from the resource name and typical list semantics. Overall, it is sufficient for an agent to select and invoke the tool correctly.

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 tool has zero parameters, so the schema carries no documenation burden. The description adds useful context by explaining the purpose of the list operation (selecting a profile for a scan), which is sufficient given there is nothing to describe parameter-specific semantics.

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 the specific verb '列出' (list) with the precise resource '扫描配置' (scan profiles), and also cites the API endpoint GET /api/v1/scanning_profiles. This leaves no ambiguity about what the tool does and clearly differentiates it from sibling tools like list_targets and list_scans.

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 '用于启动扫描时选 profile' (used to select profile when starting a scan), giving a clear use case and timing. It does not explicitly name alternative tools or exclusion scenarios, but the context makes it evident when this tool should be invoked.

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