list_vulnerabilities

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

With no annotations, the description carries the full burden, but it offers little beyond 'List vulnerabilities' and an unsupported 'filtering' claim. It does not explicitly confirm that the operation is read-only, describe the return format, or note any behavioral constraints such as pagination defaults already in the schema.

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, front-loaded sentence with no filler. However, it loses a point because the inclusion of 'filtering' is inaccurate and not supported by the schema, making the conciseness slightly misleading.

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 with fully described optional parameters, the description is nearly adequate, but the unsupported 'filtering' claim and lack of any mention of the response structure (no output schema) leave gaps. An agent could attempt to pass a filter parameter and fail.

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 schema already documents all three parameters. The description groups size/index as pagination and sort as sorting, adding minimal high-level context, but the 'filtering' mention is misleading because no filter parameter exists.

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 lists vulnerabilities, using a specific verb and resource, and mentions optional pagination, sorting, and filtering. It is distinct from siblings like get_vulnerability or update_vulnerability, but the claim of 'filtering' is not supported by any parameter in the schema, which slightly undermines accuracy.

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 description gives no guidance on when to use this tool versus alternatives. It does not mention that get_vulnerability retrieves a single vulnerability or that list_vulnerability_comments handles comments, leaving the agent without context for selection among sibling tools.

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