roboshadow_get_vulnerable_devices

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

With no annotations, the description must carry the behavioral burden. It clearly signals a read-only listing operation and discloses what each returned item contains (per-severity CVE counts and an overall CVSS score). It does not discuss pagination or ordering, but the input schema already documents pagination parameters and no side-effect profile is needed for a list operation.

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 tightly written sentence with no filler. The verb and object are front-loaded, followed by the meaningful output details. Every word adds information.

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 list tool it conveys the core purpose and output shape, but there is no output schema and no annotations, so more context would help—particularly how this endpoint relates to the many vulnerability siblings and what the response envelope looks like. Still, an agent could invoke it correctly using the documented organisationId.

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 description coverage is 100%, so the parameters are already well documented. The description adds no parameter-level meaning beyond the schema; the baseline of 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?

The description begins with a specific action and resource: 'List devices with known vulnerabilities'. It also names the returned data (per-severity CVE counts, overall CVSS score), which separates it from siblings focused on applications, CVEs, or summaries.

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 intended use is implied by the action—use it when you need a device-level vulnerability list with CVSS/CVE counts. However, it gives no explicit guidance about when to prefer this tool over overlapping siblings like roboshadow_get_device_vulnerability_summary or roboshadow_get_vulnerabilities_summary, so the agent is left to infer selection.

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