zabbix_problem_get

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

No annotations provided, and the description omits any behavioral details such as read-only nature, authentication requirements, rate limits, or pagination behavior. The agent has no insight into side effects or constraints.

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?

Extremely concise but at the cost of essential information. The single sentence does not justify its brevity, failing to provide value beyond the tool name.

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 provides no context about what the tool returns. Given the complexity of Zabbix problems (states, severities), this is severely incomplete.

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 opaque 'params' parameter with 0% description coverage. The description does not explain its structure or purpose, leaving the agent unable to construct valid calls.

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?

Description 'Zabbix API problem.get method' clearly indicates it's a retrieval operation for problems, distinguishing it from create/delete/update siblings. However, it lacks specificity about what problems are retrieved (e.g., current problems, historical).

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 on when to use this tool vs alternatives like zabbix_event_get or filters. No context about typical use cases or prerequisites.

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