zont_list_devices

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

No annotations are provided, so the description carries the full burden. It does disclose that results include device settings and that io carries per-device current states when requested, but says nothing about authentication needs, scope limits, or result size/pagination.

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?

Two short lines, front-loaded with the main action; the parameter note is separated and terse. No filler, though the load_io line is slightly clipped rather than fully formed.

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?

An output schema exists, so return-value detail is not required here, and a read-only listing tool with one optional boolean has modest demands. The only real gap is the absence of any guidance about when this enumeration is preferable to the other list/event tools.

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% — the schema only offers the bare title 'Load Io'. The description rescues that gap by explaining load_io controls whether current per-device states are returned in the io field, which the schema alone would not convey.

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?

States a specific verb and resource: retrieving the list of the user's ZONT devices along with their settings. This clearly separates it from the write-oriented siblings (zont_add_device, zont_delete_device, zont_update_device), though it never names a sibling explicitly.

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 call this versus zont_load_data, zont_raw_events, or the per-device tools; the agent must infer that this is the enumeration entry point. The load_io note explains a parameter, not a usage condition or prerequisite.

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