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

Annotations already declare read-only, idempotent, closed-world behavior, so the bar is lower. The description adds the 50-result cap and the ordering (largest rise first), which are genuinely useful behavioral facts, but says nothing about tie-breaking, the baseline comparison mechanics, or whether CVEs with no prior score are included.

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?

A single compact sentence that front-loads the resource, then the ranking, then the cap and sort order. Nothing is redundant with the title.

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 one-parameter ranked-list tool with no output schema, the essentials (what, cap, ordering) are present. It is silent on the shape of returned fields and on the 'rising exploitation' framing, which risks an agent over-reading EPSS movement as exploitation evidence.

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 coverage is 100% and the enum plus default are documented in the schema; the description only restates the three window options. It adds no extra meaning such as how a missing prior score affects a 30d comparison.

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 resource (CVEs) and a specific ranking operation (largest EPSS rise), with the window enumerated as day/week/month. It doesn't explicitly distinguish itself from the sibling get_epss_history, which an agent might read as overlapping.

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?

Use is implied by 'rising exploitation' — a ranking/digest use case — but there is no explicit when-to-use or when-to-prefer-get_epss_history guidance, and no mention of whether rising EPSS implies actual exploitation.

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