zabbix_raw_api

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

The description adds real behavioral context beyond the annotations: a blocklist exists, and write calls follow a confirm-token/preview flow. However, listing "read-only" as one of the safety rules sits awkwardly against readOnlyHint=false and destructiveHint=true, leaving the agent unsure whether writes are actually permitted here; the contents of the blocklist and what the preview step returns are not stated.

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 short sentences, zero filler, with the framing ("escape hatch") front-loaded before the safety caveat. Nothing could be removed without losing information.

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 three-parameter escape hatch with full schema coverage and no output schema, the definition covers the essential shape: what it does, that guardrails apply, and that writes need confirmation. The missing piece is which tool produces the preview token and how failures/blocked methods are surfaced.

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 description coverage is 100%, so method, params, and confirm_token are already documented in the schema, including that params may be an array for delete methods and that the token comes from a preview call. The description adds no format, syntax, or method-specific detail beyond that, so the baseline of 3 applies.

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?

"Escape hatch: call any 7.4 API method" names the specific action (arbitrary JSON-RPC method invocation) and the API version, and the word "escape hatch" signals it is the fallback rather than a primary surface. It distinguishes itself from curated siblings like zabbix_hosts or get_host_details, though it never names zabbix_search_methods or zabbix_describe_method as the pair to route through first.

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?

"Escape hatch" implies usage — reach for this when no dedicated tool covers the method — and the parenthetical hints at the guardrails applied. But there is no explicit "prefer X over this" statement despite zabbix_search_methods and zabbix_describe_method existing as obvious discovery siblings, and no guidance on when a method is disallowed.

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