CVE MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the requirement for GITHUB_TOKEN for best results and the security research purpose, which are useful behavioral constraints. However, it doesn't disclose rate limits, pagination behavior, authentication specifics beyond the token mention, or what happens when secrets are found. The description adds value but doesn't fully compensate for the lack of 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 perfectly structured and concise. The first sentence states the core purpose, the second provides important behavioral context (token requirement and usage scope), and the parameter documentation is clearly separated with examples. Every sentence earns its place with no wasted words.

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's complexity (searching GitHub for secrets), no annotations, and the presence of an output schema (which means return values are documented elsewhere), the description is quite complete. It covers purpose, usage context, behavioral constraints, and parameter semantics well. The main gap is more detailed behavioral information about how the search works and what limitations exist.

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?

With 0% schema description coverage and only 1 parameter, the description provides excellent parameter semantics. It clearly explains what the search_term parameter represents ('CVE ID, tool name, or keyword to search for in public repo files') and provides concrete examples (e.g., 'CVE-2024-1234, AWS_SECRET_ACCESS_KEY, log4j'). This fully compensates for the lack of schema descriptions.

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 specific action ('Search GitHub public repositories for potential exposed credentials or secrets') and the resource ('GitHub public repositories'). It distinguishes itself from sibling tools by focusing on secret scanning rather than vulnerability checking, reputation analysis, or other security functions listed among siblings.

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 clear context for when to use this tool ('for security research only') and specifies the type of search terms (CVE ID, tool name, or keyword). However, it doesn't explicitly state when NOT to use it or name specific alternative tools from the sibling list for different use cases.

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