zabbix_apiinfo_create

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

With no annotations, the description should disclose behavioral traits. It only indicates a create operation but fails to mention side effects, required permissions, or any constraints. The generic 'params' parameter further obscures expected behavior.

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, but this is not genuine conciseness. It lacks critical information that should be conveyed, making it under-specified rather than efficiently written.

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?

Despite having an output schema, the description does not mention the return value or provide any context about the apiinfo resource. The description is insufficient for an agent to understand the tool's place among siblings or its overall functionality.

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 0% coverage, and the description provides no explanation of the 'params' parameter. The parameter name is generic, and without additional context, an agent cannot determine what data to provide.

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 apiinfo.create method' only restates the method name without specifying what resource is created or what apiinfo represents. It is only slightly more informative than the tool name itself, providing no context about the purpose.

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 is given on when to use this tool versus alternatives like zabbix_apiinfo_get or other create tools. The description lacks context about the appropriate scenarios for invoking apiinfo.create.

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