defender_export_antivirus_health

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

Annotations already mark the operation as read-only. The description adds behavioral context by noting the links are 'short-lived' and that the report is a full export of every device, which implies a potentially large result. This enriches the annotation without contradiction.

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?

Two sentences, no fluff. The main purpose is front-loaded and the sibling alternative is appended in a compact second sentence, so every word earns its place.

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, read-only, export tool, the description is nearly complete. It tells an agent what the output is (download links), their temporary nature, and the scope. It doesn't specify report format, but this is a minor omission given no output schema or params.

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 fully describes the input. With no params to document, the description only needs to avoid implying any filter; it clarifies the all-devices scope, meeting the baseline for no-parameter tools.

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?

Description explicitly states the verb 'Get' and the resource: 'short-lived download links of the full antivirus health report of every device.' It also contrasts with the bounded sibling defender_get_device_health, making the purpose unambiguous.

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 second sentence provides an explicit alternative: 'For a bounded look at it use defender_get_device_health.' This tells the agent exactly when to choose this tool over the sibling, fulfilling the usage guidance dimension.

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