zabbix_valuemap_exists

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

The description lacks any behavioral disclosure. It does not state that this is a read-only check, what it returns (presumably a boolean), or any authentication or error conditions. Annotations are absent, so the description should cover this but fails to do so.

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 terse sentence that adds no information beyond the tool name. It does not earn its place; it is under-specified rather than concise.

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 no annotations and no output schema details provided, the description should explain behavior and return values. It does not, making the tool definition incomplete for an agent to use effectively.

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 (0% schema description coverage), and the description adds no explanation of its structure or allowed values. The agent cannot infer how to specify the valuemap to check.

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 valuemap.exists method' is a tautology that restates the tool name without explaining what the 'exists' method does. It does not distinguish this tool from siblings like zabbix_valuemap_get or zabbix_valuemap_create.

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 provided on when to use this tool versus alternatives such as zabbix_valuemap_get, which could also check existence. There is no mention of prerequisites or context for use.

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