zabbix_templategroup_get

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. It implies a read-only operation ('get'), but does not confirm idempotency, rate limits, or required permissions. The agent is left to assume standard API behavior without explicit safety guarantees.

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 concise with a single sentence, but it sacrifices informative content for brevity. It does not include front-loaded key details, making it minimally viable but not efficiently useful.

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 complexity of a Zabbix API tool and the presence of an output schema, the description should provide context on the expected return structure or common use cases. It fails to do so, leaving the agent to infer from the schema alone, which may not cover all necessary details for correct invocation.

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 fails to explain what values this parameter accepts, how to filter results, or any default behavior. This omission severely hinders an agent from constructing a correct request.

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 templategroup.get method' is essentially a tautology of the tool name, providing minimal additional insight. It states the verb 'get' and resource 'templategroup', but does not clarify what a templategroup is or how this tool differs from similar 'get' tools like zabbix_host_get or zabbix_template_get.

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 offers no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, filtering, or whether this is for listing or retrieving specific template groups. This forces the agent to rely solely on the tool name for context.

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