zabbix_usergroup_update

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

No annotations provided, yet the description fails to disclose any behavioral traits (e.g., destructive nature, permissions needed, side effects). The description adds no value beyond a method name.

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?

Extremely short but not conciseness—it is under-specified. The single sentence provides no useful structure or front-loading of key 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?

For a mutation tool with no annotations, no schema richness, and an output schema that is not explained, the description is completely insufficient to enable correct invocation.

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% with a single opaque 'params' object; description adds zero information about parameters or their semantics.

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?

Description merely restates the tool name as 'Zabbix API usergroup.update method', lacking a specific verb+resource that distinguishes it from siblings like zabbix_hostgroup_update or zabbix_usergroup_create.

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 vs alternatives; no mention of context, prerequisites, or exclusions.

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