reload_device_list

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

The description discloses that it forces a cache refresh, implying a write operation with potential side effects. It mentions return status and message, but does not detail permissions or impacts. Given no annotations, this is adequate.

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 well-structured with a clear title, usage note, and separate sections for args and returns. Every sentence adds value; no wasted words.

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?

The description covers purpose, usage context, parameter semantics, and return structure. It is fully self-contained and complete for a simple tool with one optional parameter.

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?

The description adds significant value beyond the schema by explaining the adom parameter's default (from DEFAULT_ADOM env var or 'root'). With 0% schema coverage, this is essential and well-provided.

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 it reloads the device list from FortiManager database, forcing a cache refresh. It distinguishes from siblings like list_devices and add_device by focusing on refreshing existing data rather than listing or adding.

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 'Useful after direct database changes or if device list appears stale', providing clear when-to-use guidance. However, it does not mention when not to use or explicitly compare with alternative tools.

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