zabbix_get_proxies

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

No annotations are present, so the description must carry the full burden. It only states a read operation without disclosing return format, pagination, limits, or side effects. It also does not mention default output properties or how filters behave, leaving significant behavioral aspects undisclosed.

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, concise sentence with no filler. It is front-loaded with the action and resource, making it easy to parse. Every word contributes to the core purpose, and the structure is highly scannable.

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?

For a tool with 9 optional parameters and no output schema, the description is too sparse. It does not state what the output contains, how to leverage filters, or any limitations. While the schema provides parameter-level details, the overall usage context is missing, leaving an agent under-informed.

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?

Schema description coverage is 100%, so the baseline is 3. The description's mention of 'filtering and output options' maps to the filter and output parameters, but it adds no semantic detail beyond what the schema already provides. The schema fully documents each parameter, so additional description is not necessary.

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 clearly states the action ('Get proxies') and resource ('proxies') from Zabbix. It distinguishes from sibling tools like create/update/delete proxies, though it does not explicitly differentiate from other 'get' tools beyond the resource name. The phrase 'with filtering and output options' is generic but still hints at functionality.

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. There is no mention of scenarios, exclusions, or comparisons with other Zabbix tools. The description lacks context for an agent to decide between this and similar 'get' tools.

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