defender_get_recommendations

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. However, the description adds no behavioral context beyond the annotations—no pagination behavior, response shape, or authentication notes. It neither contradicts nor enriches the annotations.

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, front-loaded sentence that states the primary purpose immediately and then gives a useful example. No filler, redundancy, or unnecessary detail. 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 read-only list tool with three optional parameters, high schema coverage, and safety annotations, the description plus schema is sufficient for an agent to invoke it correctly. The filter example fills the main semantic gap. While no output schema means return fields are not specified, that is a minor omission given the straightforward listing purpose.

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 coverage is 100% for all three parameters, so the baseline is 3. The description adds value by providing a concrete OData filter example ('remediationType eq ConfigurationChange'), illustrating how to use the filter parameter in practice. Top and skip are already well documented in the schema.

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 a clear verb and resource: 'List security recommendations'. The concrete filter example ('remediationType eq ConfigurationChange') further clarifies the tool's scope. This clearly differentiates it from siblings like defender_get_recommendation_by_id, which targets a single recommendation.

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 use this tool versus alternatives like defender_get_recommendation_by_id, defender_get_recommendation_machines, or defender_get_remediation_activities. The filter example is parameter-level advice, not usage direction, and no exclusions or alternative selection hints are provided.

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