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

No annotations are provided, so the description carries the behavioral disclosure burden. It clearly signals a read-only existence check and implies the tool returns an indication of public POC availability rather than the exploit code itself. It does not mention data sources, query edge cases, or limitations, but the core behavior is adequately conveyed for a one-line checker.

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 short sentence that front-loads the purpose with no filler. It could add a note about q's format without losing conciseness, but as written it is lean and direct.

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?

The tool is simple, has only one parameter, and an output schema exists, so the description need not explain return values. However, the missing q parameter definition and lack of guidance against overlapping CVE siblings leave some ambiguity about how to invoke it correctly. It is minimally viable but has clear gaps.

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 has one parameter, q, with no description and 0% schema description coverage. The description never states that q should be a CVE identifier or specifies its expected format, leaving the agent to infer this from the tool name and context.

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 uses a specific verb, 'Check if,' and identifies the resource ('CVE') and the exact question being answered ('has public POC/exploit code'). This makes the tool's purpose clear. It does not explicitly distinguish itself from overlapping siblings like exploit_cve or cve, but the existence-check scope is evident from the wording.

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 implies when to use the tool: when you need to know whether a CVE has public exploit code. However, it gives no explicit guidance about alternatives or when not to use it, and sibling tools such as cve, exploit_cve, and nvdcve overlap enough that explicit routing would help.

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