zabbix_mediatype_delete

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

No annotations are provided, and the description fails to disclose any behavioral traits such as authentication requirements, side effects (e.g., permanent deletion), or whether the operation is reversible. The burden falls entirely on the description.

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 a single short sentence, which is concise but omits essential information. It lacks structure such as usage examples or parameter details, making it insufficient for effective tool understanding.

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?

Context signals indicate 0% schema description coverage and an output schema is present but not described. The description does not compensate for these gaps, leaving the tool's behavior and return values largely unexplained.

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 input schema has one 'params' parameter with 0% schema description coverage and no explanation in the description. The description adds no meaning beyond the schema, leaving the agent to guess that it likely contains the mediatype ID.

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.delete method' restates the tool name and indicates deletion, but does not explain what a mediatype is or the deletion context. It is minimally clear and vaguely distinguishes from sibling tools by specifying the delete action.

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 guidelines are provided. The description does not mention when to use this tool, when not to, or any alternatives among the many sibling tools (e.g., zabbix_mediatype_get).

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