Get live controller status

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

No annotations are provided, so the description must fully disclose behavioral traits. It describes the output content (status codes and sensor readings) but omits critical details such as whether the call is read-only, any performance or rate-limiting considerations, or whether it returns raw or processed data.

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 focused sentence that efficiently conveys the tool's purpose and key outputs. It is compact and free of extraneous information, though it could be slightly more structured by separating the list of output elements.

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?

Without an output schema, the description fairly covers what to expect: overall status, per-zone and per-device status codes, and decoded sensor readings. This provides sufficient context for an agent to understand the return value shape and decide to invoke 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 input schema already provides a thorough description for the single parameter controllerId, including optionality rules. The description adds no additional meaning beyond what the schema states. With 100% schema coverage, a score of 3 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 'Live snapshot' as a strong verb+resource combination and lists specific outputs (overall status, per-zone and per-device status codes, decoded sensor readings) that clearly distinguish it from sibling tools like baseline_get_alarms or baseline_get_history.

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 the tool is for retrieving a live controller snapshot but provides no explicit guidance on when to use it versus alternatives like baseline_get_live or baseline_get_programs. The schema hints at conditional requirement for controllerId, but that is parameter-level, not usage context.

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