defender_get_remediation_exposed_devices

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

Annotations already communicate that this is a read-only, non-destructive operation. The description adds a slight behavioral nuance by saying 'still exposed', which indicates the result filters to devices whose exposure persists, but it does not describe pagination, result ordering, or other operational behaior.

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 a single, concise sentence with no filler words. It is front-loaded and every part contributes to defining the tool's action, resource, and scope.

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 simple read-only listing tool with two well-documented parameters and no output schema, the description plus annotations and schema is sufficient. An agent can choose the tool and construct a valid call using activity_id and optional top without missing critical information.

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 100%, so both activity_id and top are already fully documented with types, defaults, and constraints. The description adds no parameter-level meaning beyond what the schema provides, meeting the baseline but not exceeding it.

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 action ('List') and resource ('devices still exposed under a remediation activity'). It is distinct from sibling tools that return remediation activities or remediation activity metadata, so an agent can tell what this tool returns.

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 phrase 'under a remediation activity' gives an implied usage context: the agent should call this after it has a remediation activity ID and needs remaining exposed devices. However, it does not explicitly say when to prefer this over related tools like defender_get_remediation_activity_by_id or defender_get_remediation_activities.

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