zabbix_get_discovered_hosts

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only states the purpose and omits details such as response shape, pagination, permission requirements, or any side effects. Although likely a read-only operation, the description adds no context about behavior beyond the basic action.

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 a single, direct sentence with no unnecessary words. It is front-loaded with the verb and resource, achieving maximum economy.

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 is minimal but does not provide sufficient context for an agent to fully understand what 'discovered hosts' means or how this tool fits with alternatives. No output schema or annotations exist, so more context would be valuable, especially to differentiate from zabbix_host_get.

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 100%, so the schema already explains all parameters. The description adds no parameter-specific meaning, and per the rubric, baseline 3 is appropriate given high schema coverage.

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 'Get hosts discovered by network discovery or LLD rules' clearly states the action (get), the resource (hosts discovered), and the scope (network discovery/LLD), distinguishing it from siblings like zabbix_get_discovered_services and zabbix_host_get.

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?

No explicit when-to-use or alternative instructions are provided. The description and name imply it is for fetching discovered hosts, but it does not contrast with related tools such as zabbix_host_get or zabbix_get_discovery_rules.

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