List vulnerabilities for an endpoint

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the bar is lower; the description adds a genuinely non-obvious operational fact — a 403 is returned rather than an empty result when the API key lacks the vulnerabilities scope. It omits pagination/result-size behavior for what could be a long findings list.

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?

Two tight sentences with zero filler; the resource scope is front-loaded and the auth-scope caveat follows. Every sentence 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?

An output schema exists so return values needn't be explained, parameters are fully documented in schema, and annotations cover safety. What remains missing is scale behavior (pagination/limits) for a findings list and explicit sibling disambiguation.

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 endpoint_id, org_id, and the response_format enum are already fully documented in the schema. The description adds no extra meaning about required vs optional parameters, so baseline 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?

Specific verb+resource ('Returns vulnerability findings for one endpoint') makes it readily distinguishable from the org-wide sibling action1_list_org_vulnerabilities. It doesn't name a sibling explicitly, so it stops 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?

No when-to-use guidance and no routing to alternatives such as action1_list_org_vulnerabilities, action1_list_endpoint_missing_updates, or action1_list_cve_endpoints. The agent must infer from the name alone that this is the per-endpoint variant.

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