zabbix_get_discovery_rules

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'filtering and output options' but does not explain return format, pagination, default limits, or potential side effects. For a read-only tool, the safety profile is inferable from the name, but the description adds minimal behavioral context.

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, front-loaded sentence with no fluff. It efficiently communicates the core action and resource, though it is somewhat generic and could have included more useful detail in the same space.

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 tool's complexity (15 parameters, nested objects, no output schema, no annotations), the description is inadequate. It omits return structure, default sort/limit behavior, filter/search semantics, and any usage notes. The schema covers parameter meanings, but the description does not provide an overall context for how the tool behaves.

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 100% description coverage for all 15 parameters, so the baseline is 3. The description's phrase 'with filtering and output options' only vaguely restates what the schema already documents and adds no unique semantic value beyond the parameter 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 clearly states 'Get Low-Level Discovery (LLD) rules from Zabbix' with a specific verb and resource. It distinguishes itself from sibling tools that create or update discovery rules, though it does not differentiate from other get_* tools beyond the resource name.

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 guidance is provided on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or when another tool would be more appropriate. The only implicit hint is the 'get' verb, which suggests a read operation, but this is not explicitly stated.

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