list_devices

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

With no annotations, the description carries the full burden of transparency. It accurately implies a read-only operation via 'list' and specifies the returned fields (status, last seen time), but it omits details about pagination, ordering, or any potential performance considerations. The description is not misleading, but it adds minimal context beyond the basic action.

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, sharply written sentence that front-loads the action ('List') and key output details. It uses no unnecessary words and is appropriately concise for such a simple tool.

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 list tool, the description covers the essential return values (status, last seen time) and scope ('all IoT devices'). However, it does not describe the full device object structure (e.g., device identifier) or any limitations, which leaves minor ambiguity. Given the lack of an output schema, a bit more detail would have made it fully complete.

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 has zero parameters, and the schema is empty. As per the baseline for 0-parameter tools, the description does not need to explain parameter semantics. The description adds no parameter information, but none is required.

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 clearly defines the tool's purpose: listing all IoT devices in the user's jettyd account with status and last seen time. The verb 'list' and explicit scope 'all IoT devices' effectively distinguish it from sibling tools that focus on single devices or telemetry.

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 provides clear context for when to use this tool: when an overview of all devices is needed. It does not explicitly mention alternatives or exclusions, but the phrase 'all devices' implies it is for broad listing rather than targeted queries.

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