get_cvss_details

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds behavioral context like rejection of v2 vectors with 400 error and conditional population of temporal/environmental scores, but no contradictions. It provides sufficient extra detail beyond 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 relatively long but well-structured and informative. Every sentence adds value, including usage guidance, return field details, and rate limits. Some minor redundancy with schema could be trimmed, but overall efficient.

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 output schema exists (as indicated by context signals), the description still provides a comprehensive list of return fields and conditions, rate limits, and error handling. It fully equips the agent to use the tool correctly without needing additional context.

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 single parameter 'vector' has 100% schema description coverage, and the description's parameter details mirror the schema exactly. No additional meaning is added beyond what the schema already provides, so baseline of 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 states the tool's purpose: 'Parse a CVSS v3.x vector string into a per-metric breakdown plus a recomputed base score.' It distinguishes from siblings by specifying it handles v3.x only and points to cve_lookup for v2 detail.

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 explicitly states when to use the tool: 'Use to translate raw CVSS strings... and to verify upstream NVD scoring.' It also provides a clear exclusion: v2 vectors are rejected, with an alternative: 'read cvss_v2_vector from cve_lookup if you need v2 detail.'

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