sdcloud_list_device_licenses

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

No annotations provided; description only says 'list'. Does not disclose pagination behavior (despite pagination params in schema), read-only nature, or potential performance implications. The description carries the full burden but adds minimal behavioral detail.

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, no extraneous text. However, it is overly terse and missing crucial context, making it less useful than a concise but complete description.

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?

Given the tool has 5 params, no output schema, and many sibling tools, the description fails to mention pagination, filtering, sorting, or response structure. This is insufficient for a tool with moderate complexity.

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 80% with param descriptions for from, size, sortby, filters, but the required device_uuid lacks a description. The description does not explain that device_uuid identifies the device, nor does it add value beyond the schema for the other params.

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 states the verb 'list' and the resource 'licenses installed on a specific device'. It distinguishes the tool's scope (per device) but does not explicitly differentiate from the sibling sdcloud_get_device_license, which might be for a single license.

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?

No guidance on when to use this tool versus alternatives like sdcloud_get_device_license or other list tools. No context on prerequisites or typical use cases.

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