zabbix_proxygroup_get

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

With no annotations, the description should disclose behavioral traits (e.g., read-only, pagination, required permissions). It provides none, leaving the agent to guess that this is likely a read operation but with no details.

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?

While extremely concise, the description is under-specified and fails to earn its place. A single sentence that adds no value beyond the tool name is not efficient; it wastes the opportunity to provide minimal guidance.

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 Zabbix API and the existence of an output schema, the description should at least define what a proxy group is and how the tool fits into the monitoring workflow. It is completely inadequate for an agent to use correctly.

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 parameter with 0% description coverage. The description adds no information about the 'params' field, its structure, or how to use it to filter/fetch proxy groups.

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 proxygroup.get method' is a tautology that merely restates the tool name without explaining what the method does (retrieve proxy groups) or distinguishing it from sibling tools like zabbix_proxygroup_create or zabbix_proxygroup_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 guidance on when to use this tool versus alternatives (e.g., zabbix_proxygroup_exists, zabbix_hostgroup_get). There is no mention of context, prerequisites, or excluded cases.

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