shodan_cves_by_epss

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered. The description adds that CVEs are ranked by EPSS score, which is useful behavioral context, but it does not disclose other traits such as default ordering, pagination behavior, or response format. No contradiction with annotations.

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, focused sentence that front-loads the key action and resource. Every word contributes to understanding the tool's purpose with no filler or repetition.

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?

There is no output schema, so the description must explain what the tool returns, but it only states 'CVEs ranked by EPSS score' without specifying return fields, pagination, or whether it returns full CVE objects or just IDs. For a tool with five parameters and no output schema, this is insufficient.

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 fully documents all five parameters. The description does not add further semantic detail beyond the EPSS ranking context, making the parameter meaning purely schema-driven. Baseline 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 uses a specific verb 'Get' with resource 'CVEs ranked by EPSS score', clearly distinguishing it from sibling tools like shodan_cves_newest, shodan_cves_kev, and shodan_cve_search. It unambiguously states the tool's core functionality.

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 implies the tool should be used when CVEs ranked by EPSS score are needed, but it does not explicitly state when to use this tool versus alternatives like shodan_cves_kev or shodan_cves_newest, nor does it mention any exclusions or prerequisites.

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