zabbix_hosts

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

readOnlyHint=true already declares the safety profile, so the '[READ]' marker is largely redundant. The description does add what the result contains (hosts with interfaces and owning groups), which is useful, but says nothing about permissions, pagination, or freshness of the inventory.

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 plus a compact Args block; the resource scope is front-loaded before the parameter note. No filler, though the '[READ]' tag duplicates the annotation rather than earning space.

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 single-parameter read-only inventory call with no output schema, the description covers resource, contents, and the one parameter's behavior adequately. Only the absence of alternatives guidance keeps it from being fully 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?

Schema coverage is 0% and the schema entry for 'target' is a bare anyOf string/null with default null. The description compensates by explaining that target is a 'Zabbix target name from config' and that omitting it selects the default — meaningful semantics the schema does not carry.

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 resource ('Zabbix hosts with interfaces + owning groups') and an implicit read verb, with '(health inventory)' clarifying the intent. It is distinguishable from siblings like zabbix_hostgroups or zabbix_problems, though the description does not explicitly contrast against them.

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 '[READ]' prefix and 'health inventory' hint at when the tool is appropriate, but there is no explicit when-to-use, when-not-to-use, or named alternative among the many Zabbix and non-Zabbix monitoring siblings. The agent must infer the role from the tool name alone.

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