dss_list_devices

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

With no annotations provided, the description must fully disclose behavior. It implies a read-only operation via the verb 'List', but it does not mention pagination behavior, required parameters, or response characteristics. There is no information about side effects, authorization needs, or rate limits, leaving significant gaps.

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 sentence of eight words, with no unnecessary fluff. It is front-loaded with the action and resource, making it easy to parse. Every word earns its place.

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?

The tool is relatively simple (list operation, moderate parameter count), but with no annotations, no output schema, and a terse description, the agent is left without usage guidelines or behavioral context. The description is sufficient for a basic understanding but lacks depth for confident invocation in nuanced situations.

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 schema description coverage is 100%, meaning all three parameters (page, device_id, page_size) are described in the schema. The description adds no additional parameter context beyond what the schema provides, so a baseline score of 3 is appropriate.

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 tool's action ('List') and resource ('devices managed by Dahua DSS platform'), distinguishing it from other DSS tools like dss_list_channels. However, it does not explicitly differentiate from similar device-list tools on other platforms (e.g., iot_list_devices, tb_list_devices), so it's clear but lacks explicit sibling differentiation.

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 is provided on when to use this tool versus alternatives. The description does not mention any exclusions, prerequisites, or scenarios where another tool would be more appropriate. This leaves the agent to infer usage from the name and minimal description.

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