zabbix_dashboard_exists

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

No behavioral details are provided beyond the method name. No annotations exist, so the description must carry this burden. It does not disclose side effects (though likely read-only), authentication needs, rate limits, or return behavior.

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 short phrase that fails to provide essential information. It is under-specified rather than concise; every sentence should earn its place, and this one does not add value beyond the tool name.

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 input schema simplicity and lack of annotations, the description should compensate. It does not mention the output schema, return format, or how to construct the 'params' object, leaving the agent with insufficient guidance.

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 one parameter 'params' with 0% description coverage. The description offers no explanation of what 'params' should contain, which is critical for a nearly undocumented schema.

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 'Zabbix API dashboard.exists method' restates the tool name without providing a clear action or distinguishing it from many sibling 'exists' tools. It does not specify what 'exists' means (e.g., check if a dashboard exists by ID or name).

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 on when to use this tool versus alternatives like zabbix_dashboard_get or other exists methods. There is no mention of prerequisites, context, or when not to use it.

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