zabbix_templategroup_delete

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

There are no annotations and the description fails to disclose behavioral traits such as idempotency, side effects, prerequisites, or error conditions. The vague input schema (anyOf object/null) further obscures 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?

While brief, the description is underspecified and lacks substantive content. It does not earn its place as it adds no 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?

The description is completely inadequate for a delete operation. It does not specify required identifiers, behavior when the group contains templates, or what the output schema contains. The presence of an output schema is not leveraged.

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 single parameter 'params' has no description and zero schema coverage. The description does not explain what keys or values the object should contain, leaving the agent with no guidance on how to structure the input.

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.delete method' merely restates the tool's name, providing no additional context about what a template group is or what deletion entails. It is a tautology.

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 guidance is provided; the description does not indicate when to use this tool over sibling tools like zabbix_templategroup_create or zabbix_templategroup_get. It offers no context for invocation.

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