zabbix_alerting

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds real value beyond that: it discloses the two-step write protocol (preview, then repeat with confirm_token) and that reads return compact defaults. It does not say what data destruction looks like or what permissions are required, which keeps it from a 5.

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?

Two sentences, front-loaded with the domain and its method inventory, then the behavioral rules. The dense semicolon-separated method list is information-carrying rather than filler. Minor cost: the enumeration is heavy to parse and could have been collapsed, but no sentence is truly wasted.

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 generic JSON-RPC dispatcher with three highly schematized parameters and no output schema, the definition covers the essentials: what resources, which verbs, the two-phase write requirement, and where to get method-level documentation. The return-value shape is only hinted at ('compact defaults'), which is the main remaining gap, but the describe_method pointer mitigates it.

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 100%, so method, params, and confirm_token are all documented in the schema; the baseline of 3 applies. The description does reinforce the confirm_token workflow and that params can carry ids for deletes only indirectly. Notably it defers parameter detail to zabbix_describe_method rather than explaining method-specific shapes itself.

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 names the domain ('Zabbix alerting API') and explicitly enumerates the resources it governs: action, mediatype, script, connector, each with its supported verbs. That lets an agent separate it from siblings like zabbix_hosts or zabbix_config without opening the schema. It stops short of a 5 because the tool itself is a generic method dispatcher, so the actual operation is only known once the agent picks a method string.

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?

There is one concrete routing instruction: use zabbix_describe_method for docs and parameters, which is genuinely useful. However, there is no guidance on when to choose this tool over zabbix_raw_api (which presumably can call the same methods) or over the domain-scoped siblings, and no statement of prerequisites or exclusions. Usage is implied by the resource list rather than stated.

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