list_antivirus_profiles

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

No annotations are provided, so the description carries the burden; 'List' implies a read-only, non-destructive operation, and it usefully discloses the ADOM default resolution order and the error shape ('message'). It does not mention pagination, result limits, or required permissions, which are the main remaining unknowns for a listing call with no annotation coverage.

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?

Front-loaded with the purpose, then a short domain note, then Args and Returns. The domain note and the Returns block are somewhat verbose for a simple list tool, but nothing is actively wasteful.

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?

An output schema exists, so the Returns section is partly redundant, but the description is otherwise complete for a low-complexity, two-optional-parameter read tool. Adding pagination or ordering behavior would close the remaining gap.

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 description coverage is 0%, and the description fully compensates: adom is explained with its fallback chain (DEFAULT_ADOM env var, then "root") which is not in the schema at all, and name_filter is documented as a partial-match filter rather than exact. Both of the two parameters gain meaning beyond the bare anyOf string types.

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?

States a specific verb and resource ('List antivirus profiles in an ADOM') and adds a one-line explanation of what the objects are and where they apply (firewall policies). This clearly separates it from get_antivirus_profile and the create/update/delete siblings, though it does not name them explicitly.

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?

Implicit guidance only: 'List' plus a name_filter arg implies browse/search use, but there is no statement of when to use this instead of get_antivirus_profile for a single profile, nor any prerequisite or exclusion. Adequate but leaves the agent to infer the routing.

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