get_most_sighted_vulnerabilities

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

Annotations already convey readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds that results are ranked by sighting activity and useful for prioritization, but does not disclose additional behavioral details like pagination or sorting direction beyond what the schema already provides.

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 concise, with two sentences: the first states exactly what the tool does, and the second explains the value. Every sentence earns its place; no redundant or vague text.

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?

Given the simple scope, full schema coverage, and presence of an output schema, the description is complete. It explains the tool's purpose and how to think about the result (prioritization), and the annotations cover safety and idempotence.

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 (limit, date_to, date_from, sighting_type) are fully documented in the schema. The description does not add any extra meaning to these parameters, so the baseline score of 3 is appropriate.

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's function: 'Get vulnerabilities ranked by sighting activity.' This specifies the verb (get), the resource (vulnerabilities), and the ranking criterion (sighting activity), distinguishing it from sibling tools like search_vulnerabilities or get_recent_vulnerabilities_by_cwe.

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 provides clear usage context: it helps 'prioritize vulnerabilities with high real-world activity' and distinguish important from minor issues. It does not explicitly mention alternatives or when not to use, but the prioritization purpose implies when this tool is appropriate over siblings.

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