zabbix_module_install

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

No behavioral details are disclosed. The description does not indicate whether the operation is destructive, requires authentication, or what side effects occur. With no annotations, the description should provide this context but does not.

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 short, which could be concise, but it sacrifices meaningful content. It does not earn its place by providing value.

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 installing a Zabbix module, the description is grossly incomplete. It lacks information on return values, error conditions, and how it relates to other module management tools.

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 'params' parameter schema allows any object or null, but the description provides no guidance on its expected structure or meaning. With schema coverage at 0%, the description should compensate but fails entirely.

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 module.install method' essentially restates the tool name without defining what installing a module entails. It fails to differentiate from sibling tools like zabbix_module_create or zabbix_module_update.

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. No mention of prerequisites, allowed contexts, or conditions for calling the method.

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