wem_get_devices

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

No annotations are provided, so the description carries the full burden. It does disclose the shape of what comes back (IDs, names, connection status, module list with field names), implying a read-only enumeration, but says nothing about volume, pagination, or whether the list is scoped to a target/connection.

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?

Two sentences with zero waste: purpose and scope first, then return fields, then usage ordering. Every clause earns its place and nothing is buried.

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?

With no output schema, the description usefully enumerates the returned fields, and with no parameters there is nothing else required to invoke it. The remaining gap is the unexplained overlap with wem_get_device_status and any guidance on result size.

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 takes zero parameters, so the baseline is 4 and there is no parameter semantics to compensate for. The description correctly implies the call needs no input.

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 verb and resource ("Get all WEM devices") and enumerates the return contents: device IDs, names, connection status, and module list with Index/Type/Name. It is mostly distinguishable from siblings, but it returns connection status while a sibling named wem_get_device_status exists, and the description never explains how the two differ.

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?

"Use this first to discover deviceId, moduleIndex, and moduleType needed for other tools" gives explicit sequencing and the downstream purpose, which is strong guidance for a zero-param discovery tool. It stops short of naming the alternatives it feeds into or saying when a more targeted sibling should be used instead.

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