zabbix_user_get

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

With no annotations provided, the description carries full burden for behavioral disclosure. It fails to indicate that the tool is read-only, mention required permissions, or describe any potential side effects or limitations.

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 extremely concise (six words) but under-specified. While it is front-loaded, it fails to convey essential information; conciseness is not helpful when it omits critical details.

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 large number of sibling tools (100+) and the presence of an output schema, the description provides almost no contextual completeness. It does not help an agent select this tool over closely related ones or understand invocation details.

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 sole parameter 'params' is an object with no schema descriptions (0% coverage) and the description adds no explanation of its expected structure or purpose. The description does not compensate for the lack of parameter documentation.

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 user.get method' essentially restates the tool name 'zabbix_user_get', providing minimal additional clarity. It does not specify whether it retrieves single or multiple users, nor does it distinguish from sibling tools like zabbix_user_exists.

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 on when to use this tool versus alternatives such as zabbix_user_exists or zabbix_user_get (other user methods). The description lacks any contextual hints about prerequisites or preferred scenarios.

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