zabbix_mediatype_get

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

No annotations are present, and the description lacks any behavioral details. It does not state whether the tool is read-only, requires authentication, or has side effects. Since output schema exists, return structure is inferable but not described.

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 concise (5 words) but at the expense of essential information. It is under-specified and fails to front-load useful content.

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 large number of sibling tools and the generic input schema, the description is completely inadequate. The agent cannot reliably select or invoke this tool without external knowledge.

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 0%. The single parameter 'params' is an object with additionalProperties true, but the description offers no explanation of valid fields or how to use it (e.g., filtering, pagination). The agent has no guidance on constructing the input.

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 mediatype.get method' is nearly a tautology of the tool name. It does not explain what a mediatype is or what the tool retrieves (list, single item, etc.), and it fails to distinguish from sibling tools like zabbix_mediatype_create or zabbix_action_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 usage guidance is provided. The description does not indicate when to use this tool over alternatives (e.g., other get methods for different Zabbix entities), nor does it specify prerequisites or context.

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