zabbix_create_dashboard

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

There are no annotations, so the description carries the full burden. It specifies that a new dashboard is created, but does not disclose any permissions required, side effects (e.g., whether it can overwrite an existing dashboard), or what happens on success/failure. It also doesn't mention whether the operation is idempotent.

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?

One sentence, front-loaded with the verb 'Create', and no unnecessary words. It is appropriately short for a simple CRUD operation.

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 tool is complex (8 parameters, nested widget structures), yet the description is only a one-liner. It does not provide any high-level context about dashboard structure, page/widget requirements, or ownership defaults. The schema covers parameter details but the description offers no synthetic guidance.

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 description coverage is 100%, so the schema already documents all 8 parameters in detail. The description adds no additional parameter meaning, such as typical values or relationships, so it meets the baseline for high schema coverage.

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 the action (creating) and the resource (a Zabbix dashboard), with 'new' distinguishing it from update/delete/get dashboard tools. It is specific to dashboards, not maps, despite both being visualization tools.

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 provides no guidance on when to use this tool versus updating or deleting dashboards, nor any prerequisites or context. It does not mention alternatives or when not to use it.

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