trmnl_list_devices

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

Annotations already declare readOnly=true, idempotent=true, destructive=false and openWorld=true, so the safety profile is fully covered elsewhere. The description adds only the REST endpoint mapping and says nothing about pagination, result shape, or whether all devices or only 'my' scoped devices are returned — the one phrase that matters ('my devices') is left undefined.

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 short lines with zero waste, and the core action is front-loaded. Brevity here is not the problem — it is underspecification elsewhere, not verbosity.

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 read-only list tool with no output schema and full parameter documentation, this is minimally adequate. However, an agent still cannot tell what fields devices carry, whether results are paginated, or how 'my devices' differs from fleet devices, which the description could cheaply clarify.

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?

Only one optional parameter exists and its schema description is complete (100% coverage), so the schema carries the semantic load. The description adds nothing about the 'profile' parameter, so baseline 3 applies.

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 ("List my devices") plus the underlying endpoint (TRMNL GET /api/devices), which is unambiguous about what the tool does. It does not differentiate from the many device-related siblings such as trmnl_list_fleet_devices or trmnl_get_fleet, so it falls short of a 5.

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?

There is no guidance on when to use this versus trmnl_list_fleet_devices, trmnl_get_device, or other device-listing tools, and no stated prerequisites or scope limits. The agent must infer usage context from the name alone.

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