search_by_severity

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

No annotations provided; description only states it filters by severity. Missing details on pagination, authentication, or any side effects. A read-only filter tool should disclose at least the output nature.

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?

Single sentence is concise but lacks structure. Could separate purpose from parameter details or add a note about usage. Not verbose, but too minimal.

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 output schema exists and context signals show simple parameters, the description is functional but incomplete. Does not mention return format or that it lists CVEs meeting the severity filter.

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 0%, so description must compensate. It mentions severity values but does not explain the 'limit' parameter (default 20). Only one parameter is addressed minimally.

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?

Description clearly states verb 'Filter' and resource 'CVEs by severity', listing possible values. However, it does not distinguish from sibling tools like get_recent_cves or search_cve_by_keyword.

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?

No guidance on when to use this tool vs alternatives. Does not explain that it is for filtering specific severities while other tools handle recency, ID lookup, or keyword search.

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