List zones

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the operation is read-only, destructive, or subject to rate limits/permissions. For a list operation, the agent needs to know it's safe; the description fails to convey this.

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 sentence with no extraneous information. It is front-loaded with 'Zone configuration for a controller' which sets context. However, it could be more structured (e.g., separating the action from the content description).

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 lists the specific output fields, which is helpful. However, it does not specify return format, ordering, or pagination. Additionally, missing behavioral transparency reduces completeness for effective invocation.

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% and the parameter description already explains the optionality clearly. The tool description does not add any additional meaning or context about the parameter beyond what the schema provides, so it meets minimum expectations.

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 title 'List zones' clarifies the action, but the description focuses on the output fields ('number, name, decoder serial...') rather than explicitly stating the tool lists zones. It conveys the resource but lacks a clear verb, making it slightly vague.

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 context on when the controllerId parameter is optional vs required, which is helpful. However, there is no guidance on when to use this tool over siblings like baseline_get_programs or baseline_get_status, limiting its utility for tool selection.

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