List Camera Capabilities

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

With no annotations, the description carries the full behavioral burden. It discloses that results are authoritative and include writable flags/value constraints, and exposes the server-side topic-mapping constraint ('Never construct MQTT topics manually'), which is important non-obvious behavior. It does not discuss side effects or auth, but as a discovery/list action the read-only nature is reasonably implied.

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 scannable and front-loaded: the core purpose appears first, followed by return semantics, usage rule, and the critical MQTT warning. The final sentence mildly repeats the earlier return-value statement, so it is not perfectly lean, but it remains appropriately compact.

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 simple one-parameter tool with an output schema, the description covers the primary usage, return metadata, and a critical integration constraint. However, it leaves the camera parameter underspecified and does not explicitly route to siblings for state/health/value operations, so there is a clear completeness gap.

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 single required parameter 'camera' has no schema description (0% coverage), and the description does not explain what identifier to pass, its format, or how to discover valid camera IDs. With such low schema coverage the description needed to compensate, but it does not.

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?

States a specific action ('List all capabilities/settings') against a clear resource ('camera runtime') and names the exact content returned (authoritative names, types, writable flags, descriptions, value constraints). Calling it the 'Primary discovery primitive' clearly separates it from sibling state/health/image 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?

Gives explicit invocation guidance: use this tool before attempting unfamiliar camera settings, and never infer MQTT topics. It does not name alternative tools or exclusion cases, but the context is strong enough for an agent to know when to call it.

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