List configured FortiGates

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

The annotations already establish read-only, idempotent, non-destructive behavior, but the description adds useful context beyond them: credentials are never included in the response, and this tool orients later calls by discovering valid target names. It does not discuss rate limits or auth requirements, but for a parameterless list operation with output schema present, the disclosure is strong.

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 short sentences, front-loaded with the core purpose, then the operational guidance. Every sentence earns its place without redundancy.

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 parameterless discovery tool with annotations and an output schema, the description covers the essential context: what it lists, when to call it, how its results relate to other tools, and a key privacy guarantee. Nothing needed for correct invocation is missing.

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 zero parameters, the baseline is 4. The description does not need to explain parameters for this tool, though it helpfully explains that other tools take an optional target argument derived from this tool's results.

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 specific verb and resource: 'List the FortiGate appliances this server can reach.' It clearly distinguishes this discovery/orientation tool from the many sibling list_* tools, which list configuration objects rather than reachable appliances.

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?

It explicitly says to call this first when several appliances may be configured, explains why (every other tool takes an optional target argument), and clarifies that the target argument can be omitted when exactly one appliance is configured. This gives direct when-to-use guidance and the condition for the alternative behavior.

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