run_posture_scan

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

The description discloses that scans run concurrently, results are combined and optionally filtered, and a shared cache is updated. However, with no annotations, it lacks details on side effects (e.g., whether scans modify data), permissions needed, or runtime implications.

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 two sentences long, with the first sentence providing the core action and the second adding cache update context. It is concise and front-loaded, but could include parameter details without becoming verbose.

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?

Given the tool has 5 parameters, no annotations, and no schema descriptions, the description is insufficient for correct invocation. It lacks parameter explanations, usage context, and behavioral details beyond the basic operation.

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?

With 0% schema description coverage, the description does not explain the parameters. Terms like app_id, rule_id, severity, and expiry/duration fields are mentioned only as parameter names, so the description adds no meaning beyond the names themselves.

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 runs app registration and Conditional Access scans concurrently and returns a combined, optionally filtered PostureScanResult. It also mentions updating a cache, which distinguishes it from sibling tools like 'audit_app_registrations' and 'scan_conditional_access_gaps' that likely run single scans.

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 description implies the tool is for running both scan types together and filtering results, but it does not explicitly state when to use this tool versus the individual sibling tools or provide any when-not scenarios.

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