zabbix_get_dashboards

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

No annotations are provided, so the description carries the full burden. It only states that the tool gets dashboards and mentions filtering/output options, but does not disclose return format, pagination, default limits, or that it is a safe read-only operation. The name 'get' implies read-only, but explicit behavioral context is missing.

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 a single short sentence that is immediately understandable and wastes no words. It front-loads the core purpose and a couple of key capabilities.

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?

For a tool with 10 parameters, no annotations, and no output schema, the description is minimal. It relies heavily on the schema for parameter details, but does not explain the overall response structure or any behavioral nuances, such as how filtering interacts with output or whether wildcards are supported. It is adequate but not complete for a tool with this complexity.

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 already describes all 10 parameters at 100% coverage, so the bar is lowered. The description adds only a high-level hint about filtering and output options, which partially corresponds to filter/search/output/sortfield parameters, but it does not provide any additional meaning beyond the schema property descriptions.

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 uses the specific verb 'Get' with the resource 'dashboards', clearly identifying this as a read operation for Zabbix dashboards. The phrase 'with filtering and output options' highlights distinguishing capabilities, differentiating it from create/update/delete dashboard siblings.

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 this tool should be used when retrieving dashboards, but it does not explicitly state when to prefer it over other get_* tools or provide exclusions/alternatives. There is no guidance on when to use filtering options versus a simpler call.

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