check_exploit_availability

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

No annotations provided, but description only mentions search and sorting by star count. Lacks details on rate limits, authentication, or what 'public' means. Insufficient for a tool with no annotation support.

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?

Three succinct sentences plus Args section. No redundancy, clear and front-loaded purpose.

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?

For a single-parameter tool with output schema, description is adequate but omits sorting details or limitations. Could be more complete given sibling density.

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?

Single parameter cve_id has zero schema description coverage. Description adds format example 'CVE-2021-44228', providing clarity beyond the schema's type definition.

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 verb 'Search GitHub' and resource 'public proof-of-concept exploit repositories for a CVE'. This differentiates it from sibling tools like check_poc_exists or lookup_cve.

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 guidance on when to use this tool versus alternatives such as check_poc_exists. With many similar sibling tools, explicit when/when-not is missing.

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