list_vulnerabilities

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

The readOnlyHint annotation already declares this is a read operation, and the description adds context about the data source (Shodan) and the relationship to service observations. It does not disclose pagination behavior or what happens when no vulnerabilities are found, but given the annotation coverage this is acceptable but not rich.

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 with no filler or redundancy, and it front-loads the core action and resource. It is concise, though it sacrifices important parameter and usage detail.

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?

With three parameters, one required, and zero schema descriptions, the tool description does not provide enough context to invoke it confidently. An output schema exists, but the agent still lacks guidance on how to populate report_id or interpret the meaning of limit and offset in this context.

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 0%, and the description does not mention report_id, limit, or offset at all. An agent gets no additional meaning about what report_id refers to or how pagination works beyond the raw parameter names.

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 states a specific action ('returns') and resource ('vulnerability candidates and product/observation information associated by Shodan'), so the agent can understand what the tool produces. However, it does not explicitly contrast with sibling tools like list_assets or get_evidence, so differentiation relies mostly on the tool name.

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?

There is no guidance on when to use this tool versus alternatives, and no mention of prerequisites such as obtaining a valid report_id. The context is only implicit from the tool name and required parameter.

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