search_recent_cves

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

With no annotations provided, the description must disclose behavioral traits. It states it 'Get recently published CVEs', which implies a read operation, but fails to mention pagination, ordering, or what constitutes 'recent' given the parameters. Lacks important details for safe invocation.

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, front-loaded sentence that communicates the core purpose without extraneous words. Highly concise and efficient, earning top score.

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 tool has 4 optional parameters, no output schema, and no annotations, the description is somewhat minimal. It conveys the basic purpose but does not elaborate on behavior like pagination, result format, or edge cases. Adequate but not complete.

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?

The schema description coverage is 100%, so the tool description does not need to add extra parameter meaning. However, it adds no additional context beyond the schema's descriptions. 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 clearly indicates the tool retrieves recently published CVEs within a date range, using a specific verb ('Get') and resource ('recently published CVEs'). While it hints at a specific scope, it does not explicitly differentiate from sibling tools like 'search_cves' which also handle date ranges, but it is still clear enough.

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 no guidance on when to use this tool versus alternatives (e.g., 'search_cves' for general searches). It does not specify prerequisites, exclusions, or context that would help an agent decide between siblings. Usage is only implied.

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