zabbix_hanode_create

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

With no annotations, the description fully relies on behavioral disclosure. It offers none: no mention of side effects, permissions, idempotency, or output characteristics beyond the bare method name.

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 sentence, but it is under-specified rather than concise. It sacrifices informativeness for brevity, lacking essential details.

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 complexity of Zabbix API and many sibling tools, the description is completely inadequate. It does not explain the tool's purpose, input expectations, or return values, despite an output schema existing.

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 parameter 'params' with no description and 0% schema coverage. The description adds no meaning to this parameter, failing to indicate required fields or structure.

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 hanode.create method' is a tautology, merely restating the tool name. It provides no information about what a hanode is or what creating one entails, failing to distinguish from siblings like hanode_get or hanode_update.

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. The description lacks any context about prerequisites, scenarios, or comparison with other hanode tools.

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