zabbix_valuemap_get

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

No annotations provided, so description must disclose behavior. It fails to mention whether the tool is read-only, supports filtering, returns all items, or requires authentication. Almost no behavioral context.

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 short but under-specified. The single sentence does not earn its place as it provides negligible utility. Better to expand with key details than remain this sparse.

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 generic input schema and lack of annotation, the description is woefully incomplete. It omits essential information about return format, filtering capabilities, and typical usage, making it nearly useless for correct tool selection.

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?

Input schema has a single 'params' object with additionalProperties: true, implying arbitrary keys. Description adds no meaning to this parameter, and schema description coverage is 0%, leaving the agent without guidance on valid filter fields.

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 merely states 'Zabbix API valuemap.get method', which restates the tool name without explaining what valuemaps are or what 'get' retrieves. It is a tautology with minimal clarification.

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 over siblings like valuemap_create or valuemap_exists. No context about filtering, prerequisites, or typical use cases.

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