zabbix_dhost_get

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

The description does not disclose any behavioral traits beyond the tool name. There are no annotations, so the description carries full burden. It fails to indicate whether the tool is read-only, requires authentication, or has side effects. An output schema exists but is not referenced.

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 very short, but it sacrifices necessary detail. While conciseness is valued, this is under-specification. The single sentence does not earn its place as it adds no value beyond the tool name.

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?

Given the complexity of the Zabbix API and the large number of sibling tools, the description is severely incomplete. It does not explain the purpose, parameters, or usage context. The presence of an output schema does not compensate for the lack of descriptive context.

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 a single parameter 'params' with no description (0% schema description coverage). The description does not explain what keys or values should be provided in the params object, leaving the agent without guidance on how to construct the request.

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 'Zabbix API dhost.get method' essentially restates the tool name and does not clarify what 'dhost' refers to or how it differs from siblings like 'zabbix_host_get' or other 'get' tools. The title is null, providing no additional context.

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 guidance is provided on when to use this tool versus alternatives (e.g., zabbix_host_get, zabbix_dhost_create). The description lacks any context about filtering, prerequisites, or typical use cases.

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