panelica_antivirus_post_v1_antivirus_scan

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

The annotations already carry readOnlyHint=false and idempotentHint=false; the description reinforces this with 'Mutating: changes server state' and adds the security:write scope requirement. However, it does not disclose whether the scan runs asynchronously, what side effects occur, or how the created scan can be tracked.

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 compact and well ordered: action first, then HTTP method, category, required scope, and mutating flag. Every line carries one distinct piece of operational information with no filler.

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 create operation with an opaque body and no output schema, the description omits the request payload shape, whether the scan is asynchronous, and how the result relates to the sibling panelica_antivirus_get_v1_antivirus_scan_id endpoint. The sibling polling pattern is strongly implied but never connected.

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 only parameter is a free-form body whose schema says it is not statically declared, so the agent gets no actionable field-level semantics from either the schema or the description. The high schema-description coverage signal gives a baseline of 3, but the provided description is essentially a placeholder pointing to API docs.

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 states 'Create scan' with HTTP POST /v1/antivirus/scan and category Antivirus, giving a clear verb and resource. It does not explicitly differentiate from the sibling GET antivirus tools, though the POST verb and endpoint path make the distinction fairly obvious.

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?

There is no guidance on when to create a scan versus checking antivirus status or quarantine, and no mention of polling a scan by ID after creation. The description provides operational metadata like required scopes and mutating behavior, but no context for choosing this tool over alternatives.

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