panelica_antivirus_post_v1_antivirus_scan

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

No annotations provided, so description covers behavioral aspects: starts a scan (side effect), path restrictions, prerequisite daemon. Could mention if asynchronous or how to monitor progress.

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?

Three clear sentences plus HTTP info and category. Front-loaded with purpose. No redundant 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?

Missing parameter specification (path supposedly in schema, but empty). No output schema, so agent doesn't know return value (e.g., scan ID). However, covers usage and permissions adequately for a simple tool.

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?

Input schema has 0 parameters; baseline 4 per guidelines. Description mentions 'specified path' but schema has no param, which is a minor inconsistency, but overall no params to describe.

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 the tool starts an antivirus scan on a specified path, and lists scan types (quick, full, custom). It differentiates from sibling tools like get_scan_id and get_quarantine.

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?

Provides scan types and permission restrictions (non-admin users only /home/ paths). Also notes ClamAV daemon must be running. Does not explicitly state when not to use or alternatives, but context is adequate.

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