zabbix_api_list

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

Discloses that methods are 'discovered dynamically from Zabbix API', adding behavioral context beyond the schema. No annotations provided, description carries burden well but lacks mention of potential network call or idempotency.

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?

Three sentences are front-loaded with purpose and usage, but third sentence is slightly redundant. Still clear and well-structured.

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 simplicity (one optional parameter, output schema exists), description fully covers purpose, usage context, and discovery nature. No gaps for an agent to invoke correctly.

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 coverage is 100% and description only paraphrases the schema's parameter description ('e.g., 'host', 'item'. If omitted, returns all'). Adds no novel semantic insight beyond what the schema already provides.

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 clearly states 'Get available Zabbix API objects and methods' with a specific verb and resource. Distinguishes from siblings zabbix_api and zabbix_api_docs by indicating it lists available methods before use.

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?

Explicitly says 'Call this to discover what API methods are available before using zabbix_api()', providing direct guidance on when to use and suggesting it as a prerequisite for the sibling tool.

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