unifi_protect_list_chimes

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

The readOnlyHint annotation already establishes that this is a safe read operation, and the description adds that the result includes volume and paired doorbell cameras. However, it does not mention whether the response is an array, whether pagination applies, or any authentication requirements, so some behavioral detail remains implicit.

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?

A single sentence that is front-loaded with the action and resource, followed by the relevant output details. Every word earns its place; there is no filler or redundant restatement of the tool name.

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 zero-parameter, read-only list operation, the description is sufficient: it states what is listed, which fields are included, and the description is unambiguous given the sibling context. With no output schema, the description still conveys the essential return-value content without overcomplicating the tool.

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 tool accepts zero parameters, so there is no parameter confusion and schema coverage is trivially complete. The description therefore does not need to explain argument semantics; the baseline for a zero-parameter tool is appropriate.

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 a specific verb 'List' and identifies the exact resource: UniFi Protect chimes. It also states the meaningful output fields (volume and paired doorbell cameras), which distinguishes it clearly from sibling list tools that target cameras, lights, sensors, or viewers.

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 resource scope is explicit: use this tool when you need chime information, not camera, light, sensor, or viewer data. It does not name alternative tools or provide when-not conditions, but the noun 'chimes' supplies clear context for routing.

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