get_vuln_stats

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

No annotations; description only mentions basic functionality (counts, distributions). No disclosure of authentication needs, read-only nature, or performance characteristics.

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?

Very concise with a clear title and a single functional sentence. Every sentence contributes, though structure could be enhanced with bullets.

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?

Adequate for a simple stats tool with output schema. However, missing detail on how the 'period' parameter affects the output.

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%, but description adds no information about the 'period' parameter beyond what schema already provides. Baseline 3 would require at least minimal mention.

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 it provides vulnerability statistics (counts, distribution by severity and status), distinguishing it from siblings like get_vulnerability (single vuln) and list_vulnerabilities (detailed list).

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 explicit guidance on when to use this vs other tools like list_vulnerabilities or generate_report. Implied but not stated.

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