openwisp_list_device_commands

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

No annotations are provided, so the description must carry the behavioral load. Including the HTTP GET endpoint signals a non-mutating read, which is genuinely useful, but it says nothing about pagination, ordering, result size, or whether empty results are returned for devices with no commands.

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?

One sentence plus a category tag and endpoint path, with the purpose front-loaded and no filler. Slightly denser than needed given how little it says, but nothing is wasted.

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 single-parameter read-only listing tool with a fully documented schema and no output schema, the description plus endpoint gives an agent everything required to invoke it correctly. The missing pagination and ordering notes are minor omissions rather than blockers.

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?

There is a single required parameter (device_id) with 100% schema description coverage ('Device UUID or ID'), so the schema does the work. The description adds no format or constraint detail beyond the endpoint path template. Baseline 3 applies when schema coverage is complete.

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 states a specific verb and resource ('List commands previously issued to a device') and includes the category tag, so the agent understands what it does. It does not explicitly differentiate from the close siblings openwisp_get_device_command or openwisp_execute_device_command, which is the only thing keeping it from 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?

Usage is only implied: 'previously issued' suggests a historical listing versus openwisp_get_device_command for a single record and openwisp_execute_device_command for issuing a new one. The description never states when to prefer this tool or what to use instead, leaving the agent to infer the routing.

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