zins_get_iot_device_stats

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

Annotations already indicate readOnlyHint=true. The description adds behavioral detail: it returns a single current-state object with total and per-classification counts, and explains empty results. It does not contradict annotations.

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 three sentences: purpose, output structure, and empty result interpretation. It is front-loaded and every sentence adds value 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 simple, read-only tool with one optional parameter and no output schema, the description covers purpose, output structure, statefulness, and edge cases. The only missing piece is explanation of the 'limit' parameter, but overall it is adequately complete.

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 input schema has one optional parameter 'limit' (default 50) with no description in schema (0% coverage). The description does not mention this parameter, so it adds no meaning about its purpose or effect (e.g., whether it limits entries or some other aspect).

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 the tool's purpose: 'Get IoT device statistics and classifications.' It specifies the verb (Get), resource (IoT device stats), and adds 'Read-only analytics.' This distinguishes it from sibling tools like zins_get_cyber_incidents or zins_get_casb_app_report, which cover different analytics areas.

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?

The description provides usage context by noting 'No time window — this reflects the present network state,' implying it's for current snapshots. However, it does not explicitly state when to use this tool over alternatives, nor does it mention prerequisites or limitations.

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