openwisp_get_device_command

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

With no annotations, the description carries the full behavioral burden. It discloses the HTTP method (GET), which signals a non-mutating read, but says nothing about auth requirements, whether the command may still be pending, error handling, or what the returned details contain.

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?

A single compact sentence plus endpoint reference, front-loaded with the category tag and the verb first. No waste, though the parenthetical endpoint is largely redundant with the schema.

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 two-parameter read tool with no annotations and no output schema, the description is minimally adequate: it identifies the operation but gives no sense of what 'details' are returned (status, exit code, output payload) or any failure/permission behavior an agent might need.

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 coverage is 100%, so both parameters are already documented as 'Device UUID or ID' and 'Command UUID or ID'. The description only mirrors parameter placement via the URL template, adding no new semantics such as accepted formats or alternate identifiers; 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 ('Get details for a previously executed device command') and the 'previously executed' qualifier distinguishes it from the sibling openwisp_execute_device_command and openwisp_list_device_commands. It stops short of naming those siblings, but the scope is unambiguous.

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 phrase 'previously executed' implies the tool is for retrieving an existing command's record rather than issuing one, which is useful routing context. However, it never states when to use this versus openwisp_list_device_commands or what prerequisites (e.g., command_id must come from execute) apply.

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