zabbix_maintenance_exists

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only says 'exists method' implying a boolean return, but it does not disclose side effects (none likely), authentication needs, rate limits, or what constitutes existence. Critical behavioral context is missing.

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 very brief (one short sentence), but it sacrifices necessary information for brevity. It is under-specified rather than concise, lacking critical details.

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 tool's simplicity (one optional parameter, output schema present), the description fails to cover even basic usage. It does not explain the output schema, the meaning of existence, or how the parameter filters. The description is incomplete for an agent to use effectively.

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 has 0% description coverage, meaning no descriptions for 'params'. The description does not explain what the parameter object should contain (e.g., maintenance IDs, filters). The agent has no way to know how to construct the input correctly.

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 states 'Zabbix API maintenance.exists method,' which indicates it checks existence of a maintenance object, but it does not specify what parameters are required or what exactly it checks against (e.g., by ID or filter). This is somewhat vague, as it merely restates the method name without adding clarity.

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 like maintenance.get or maintenance.create. There is no mention of prerequisites, typical use cases, or situations to avoid, leaving the agent without decision support.

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