list_ip_pools

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

No annotations are provided, so the description carries the full burden. 'List' implies a read-only enumeration, but it discloses nothing about permission requirements, whether vdom=null means all VDOMs, pagination, or result size, and never clarifies whether ARP reply is a returned flag or a filter.

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?

A single compact sentence with the resource up front and the returned fields in a parenthetical. Nothing is wasted, though the terseness leaves room for one more clause of guidance without becoming bloated.

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 two-parameter read tool with no output schema, the description covers the resource and the shape of the returned records. It stops short of explaining the required device scoping and the vdom default, which an agent needs to call it correctly.

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%: device_id is documented as the FortiGate identifier and vdom as the Virtual Domain, so the schema does the heavy lifting. The description adds nothing about either parameter, leaving the baseline 3 appropriate.

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?

Names a specific verb and resource ('List NAT IP pools') and enumerates the main returned attributes (type, start/end IP, ARP reply). An agent can tell what it does without opening the schema, though it doesn't explicitly contrast with the closest sibling, list_central_snat_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 when-to-use guidance, no prerequisites, and no mention of alternatives such as list_central_snat_rules or list_static_routes for related NAT/routing data. The agent must infer context from the name alone.

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