zabbix_connector_get

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

No annotations provided and description does not disclose behavioral traits such as read-only nature, required permissions, pagination, or response format. 'get method' implies read, but not explicit. Fails to add value beyond the tool name.

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?

Extremely short but underspecified. A concise description would still provide meaningful content. This is not concise; it is vacuous.

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 numerous sibling connector tools, the complexity of Zabbix connectors, and the presence of an output schema, the description should explain what the tool returns and how to use the params. Completely inadequate.

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?

Input schema has one parameter 'params' with no description and 0% schema coverage. Description adds no explanation of what goes in params (e.g., filter criteria, connector IDs). Completely fails to compensate for missing schema descriptions.

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?

Description says 'Zabbix API connector.get method' which is barely more than the tool name. It does not specify what a connector is or what the get method returns (e.g., list all connectors or get by ID). Fails to distinguish from sibling tools like zabbix_connector_exists or zabbix_connector_update.

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. With many sibling CRUD operations for connectors, the description should clarify usage context (e.g., 'Use to retrieve connector details by ID or list connectors with filters'). Missing entirely.

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