firewall_rules

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

Annotations already declare this a read-only, idempotent, non-destructive operation, so the safety profile is covered. Beyond that, the description adds meaningful behavioral context about the returned data: expansion of IP groups, parent-policy groups first, inclusion of threat intel/IDPS/DNS proxy settings and classic rules, and that missing policy data is reported as unknown.

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?

Four tight sentences, front-loaded with the processing order that matters most for interpretation. Each sentence conveys a distinct fact (ordering, policy precedence, IP group expansion, included settings) with no filler.

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?

With no output schema, the description does a fair job describing returned contents and ordering, but it omits what 'target' accepts and how this differs from search_firewall_rules. For a tool with only one param and a sibling overlap, more routing and parameter detail is needed.

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% for the single required 'target' parameter, and the description says nothing about it — not its format, accepted values, or whether it identifies a subscription, firewall, or policy. With one required param and no schema text, the description should compensate but does not.

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 names the specific resource (Azure Firewall / Firewall Policy rules) and details its ordering (DNAT, network, application) and contents, so the agent knows exactly what it returns. However, it never states the operation explicitly (list/get) and does not distinguish itself from the close sibling search_firewall_rules.

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, despite search_firewall_rules being an obvious sibling for filtered lookups. The description describes output content only and gives no trigger conditions or exclusions.

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