zabbix_import_compare_configuration

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

With no annotations, the description carries the full burden. It discloses the critical non-destructive behavior ('without actually importing'), which is valuable. However, it does not describe what the comparison output looks like, whether it validates syntax, or any error conditions, leaving the agent with incomplete knowledge.

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 with zero wasted words. It conveys the core purpose and key differentiator immediately, making it highly efficient.

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 a rich nested input schema, there is no output schema, and the description does not explain what the comparison result returns (e.g., diff, report, success message). For an agent to correctly invoke and interpret this tool, that missing context is significant. The minimal description leaves a clear gap.

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 schema provides 100% coverage with descriptions for all three parameters (format, source, rules). The tool description itself adds no parameter-specific meaning beyond what the schema already offers. The baseline of 3 applies because the schema does the heavy lifting.

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 tool's purpose with a specific verb ('Compare configuration') and resource ('for import'), and explicitly distinguishes it from actually importing by saying 'without actually importing'. This differentiates it from sibling tools like zabbix_import_configuration and zabbix_export_configuration.

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 implies the use case: to preview a configuration import before committing. It clearly contrasts with 'actually importing', providing context for when to use this tool. However, it does not explicitly name alternatives or provide exclusions, so it stops short of a perfect score.

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