zabbix_get_services

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

With no annotations, the description fails to state that this is a read-only operation, that it returns a list of services, or any behavioral constraints such as pagination or auth requirements. The phrase 'with filtering and output options' only echoes schema capabilities without adding 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?

The description is a single, front-loaded sentence of nine words with no redundant phrasing. It wastes no words and is easy to parse at a glance.

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 the tool's complexity (15 parameters, nested objects, no output schema), the description provides only a high-level summary. It does not explain return value shape, common use cases, or what distinguishes business services from other service types, making it incomplete for an agent to decide whether to invoke it.

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 covers 100% of parameters with descriptions, so the baseline is 3. The description's reference to 'filtering and output options' aligns with schema fields but adds no semantic value 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?

The description clearly identifies the tool as retrieving business services from Zabbix, with 'business services' distinguishing it from related tools like zabbix_get_discovered_services or zabbix_get_service_sla. The verb 'Get' and resource 'business services' are specific and accurate.

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?

The description provides no guidance on when to use this tool versus alternatives. It merely states the action without mentioning prerequisites, typical scenarios, or exclusions (e.g., use zabbix_get_service_sla for SLA calculations).

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