zabbix_role_exists

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

No annotations are provided, and the description does not disclose any behavioral traits such as side effects, authorization requirements, or whether it is read-only. For a tool with no annotations, the description must provide this context but fails entirely.

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 extremely short, consisting of only a few words. While concise, it is under-specified and provides minimal information, making it more of a placeholder than a helpful description.

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 and the presence of an output schema (not shown), the description should at least explain what the tool returns (e.g., boolean). It does not, and it lacks any context about prerequisites or behavior, resulting in very low completeness.

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 a single parameter 'params' with no documentation and 0% schema description coverage. The description adds no meaning about what this parameter should contain, leaving the agent without guidance on how to provide the role identifier.

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 role.exists method' indicates the tool checks if a role exists, which is a clear verb+resource combination. However, it's terse and does not elaborate on what 'exists' means precisely. It distinguishes from siblings like 'get' but could be more explicit.

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 vs alternatives like 'zabbix_role_get'. The description does not mention context or conditions for usage, leaving the agent to infer from the name.

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