zabbix_user_create

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

No annotations provided, and the description adds no behavioral information. It does not disclose whether the tool is idempotent, requires authentication, or what happens if the user already exists.

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 very short (one phrase), but it is under-specified. Being concise is not helpful when essential information is omitted.

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 lack of annotations, minimal schema coverage, and no output schema details provided, the description fails to give an agent enough context to use the tool correctly. It lacks any explanation of expected inputs, outputs, or side effects.

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 a single parameter 'params' with no description and 0% schema coverage. The description does not explain what 'params' should contain, leaving the agent without any guidance on how to structure the request.

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 states 'Zabbix API user.create method', identifying it as a creation operation for users. It distinguishes from sibling tools like zabbix_user_delete, zabbix_user_get via the verb 'create', but lacks detail on what creating a user entails.

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 versus alternatives like zabbix_user_update or zabbix_user_get, nor does it mention prerequisites or context.

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