template_create

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the safety profile is known. The description adds domain context (what templates are for) but does not disclose additional behavioral traits such as error behavior, idempotency nuances, or required permissions beyond what 'create' implies. It neither contradicts the annotations nor enriches them significantly.

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 well-structured with a clear topic sentence followed by brief rationale. It is not overly verbose and front-loads the core action. The second sentence adds value by explaining why custom templates matter, though it could be trimmed slightly. Overall, it is efficient and easy to scan.

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 there is an output schema and the annotations cover the safety profile, the description adequately covers the use case rationale. It explains the purpose of templates and when creating one is beneficial. No critical information is missing for an agent to invoke the tool correctly, though it could mention that the 'host' is technically the template's technical name (a nuance already in the schema).

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?

Schema coverage is 100%, so all parameters have descriptions. The high-level description ('Templates define the monitoring configuration...') provides background but does not add parameter-specific details beyond what the schema already offers. The baseline of 3 applies because the schema handles the bulk of parameter documentation.

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 clearly states 'Create a new template in Zabbix.' with a specific verb and resource. It differentiates from sibling operations like template_update and template_delete by focusing on creation. The additional context about reusability and standardized monitoring further clarifies the purpose.

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 implies usage by explaining the benefit of templates ('enables standardized monitoring') but does not explicitly state when to use this tool versus alternatives like template_update. There is no mention of prerequisites or exclusions. The guidance is implicit rather than directive.

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