check_poc_exists

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

With no annotations, the description must disclose behavioral traits. It mentions the sources searched (GitHub, Exploit-DB, Nuclei) but does not discuss whether the tool is read-only, potential rate limits, or the nature of results (existence vs. details). Basic transparency is provided, but more detail would be beneficial.

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 concise sentence with no wasted words. However, given the parameter count and need for semantics, it is slightly under-specified. Remains efficient but could be expanded without harming conciseness.

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?

Although an output schema exists (reducing the need to explain returns), the description lacks parameter explanations and usage context. With 3 parameters and 0% schema coverage, the description is incomplete for an agent to use the tool correctly.

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 description coverage is 0%, so the description must compensate. However, it does not explain any of the three parameters (cve_id, include_github, include_exploitdb). It fails to add meaning beyond the schema, leaving the agent without guidance on how to use the parameters.

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 'Search for proof-of-concept exploits across GitHub, Exploit-DB, and Nuclei templates.' It specifically identifies the action (search), the resource (PoC exploits), and the scope (multiple sources), distinguishing it from siblings like check_exploit_availability and check_kev.

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 usage for finding PoCs but offers no explicit guidance on when to use this tool versus alternatives (e.g., check_exploit_availability, check_kev), nor does it mention when not to use it. Usage context is implied but not clearly defined.

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