watchface_get_device_info

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

With no annotations, the description carries the full burden. It adds useful behavior: unknown Hardware is rejected, PIXOO64/TimeGate rely on discovery or explicit hardware profiles, and AstroToo needs a capability query first. But it does not explicitly state that the operation is read-only, nor does it describe auth needs or response shape.

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 front-loaded with the core purpose and then layers device-specific caveats efficiently. It is dense but mostly justified for a multi-device tool; the final sentence about legacy 800x1280 examples is somewhat tangential but still clarifies context.

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 one optional nested parameter with full schema coverage and no output schema, the description covers device routing and hardware validation well. However, it describes the return value only generically as 'product profile and LAN capabilities' and omits read-only/safety context that would be important without annotations.

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 description coverage is 100%, so the schema already documents target.host, port, model, hardware, and timeoutMs. The description adds meaning by clarifying that target.hardware is a device profile rather than firmware, and by explaining model-specific routing, but it does not add syntax or examples beyond the schema.

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 opens with a specific verb and resource: 'Return the product profile and LAN capabilities.' It also distinguishes device families (TimesFrame/AstroToo vs PIXOO64/TimeGate), though it does not explicitly name sibling tools like pixoo64_get_device_info or timegate_get_device_info.

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?

It gives some procedural guidance, such as 'For AstroToo, first query hardware/capabilities' and 'Unknown Hardware is rejected.' However, it does not clearly state when to use this unified tool versus the device-specific siblings, leaving the agent to infer the routing decision.

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