list_vulnerable_items

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds useful behavioral context by noting that results are curated fields ordered by descending risk score.

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 two sentences, front-loaded with the core purpose and table name, then immediately covering filters and return ordering. Every sentence carries useful 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?

Although there is no output schema, the description states that curated fields are returned and ordered by descending risk score. Combined with the fully documented input schema and annotations, this is sufficient for correct invocation, though more detail on returned fields could help.

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 the schema fully documents all seven parameters. The description repeats a subset of filters but adds no syntax or meaning beyond what the schema already provides.

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 names a specific verb (List) and resource (USEM Vulnerable Items / sn_vul_vulnerable_item), making the tool's function immediately clear. It does not explicitly distinguish itself from sibling tools such as get_vulnerable_item or list_vulnerabilities, so it falls short of 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?

It states which filters are available, implying the tool is used to retrieve filtered vulnerable-item lists. However, it gives no guidance on when to choose this tool over alternatives like get_vulnerable_item or list_vulnerabilities.

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