zabbix_connector_exists

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

With no annotations, the description carries the full burden of behavioral disclosure. It fails entirely, not stating whether the tool is idempotent, what permissions are needed, or what the output format is (beyond an output schema being present).

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?

While the description is very short, it lacks substantive information. Every sentence should add value; this one merely restates the name. It is not front-loaded with key usage or behavior 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?

Despite having an output schema, the description is severely incomplete. It omits essential context about what the tool checks, how to invoke it, and what the response signifies. An agent cannot reliably use this tool based solely on the description.

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 zero description (0% coverage). The description adds no meaning about what the parameter should contain (e.g., filter criteria like connector ID). The tool is effectively unusable without parameter guidance.

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 connector.exists method" is essentially a tautology, restating the tool name without specifying what 'exists' means (e.g., checking existence of a connector by ID or name). It does not distinguish from sibling tools like zabbix_connector_get, which retrieves connector details.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives (e.g., zabbix_connector_get), nor does it mention any prerequisites or exclusions.

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