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

Goes well beyond the readOnly/non-destructive annotations by disclosing source coverage, that GitHub PoCs are not ingested, and that an empty result is not proof no exploit exists. That negative-space disclosure is exactly the behavioral context an agent needs to reason about result trustworthiness.

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 sentences, front-loaded with what is returned, then the excluded source, then the caveat. Every sentence carries distinct information with no repetition of the name or title.

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?

With no output schema, the description still conveys return shape (module, type, rank, publisher citation) and the main coverage caveat. Only the semantics of verified_only and any ordering or pagination behavior remain unaddressed.

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 coverage is 100%, so cve_id and verified_only are already documented in the schema. The description adds no meaning about what 'verified' means or how it filters Metasploit rank, leaving that at the baseline for fully covered schemas.

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?

States a specific verb and resource (exploit references for a CVE) plus the exact sources covered: Exploit-DB records and Metasploit module metadata. It also carves out a sibling, stating nuclei detection templates live on get_cve_details, so an agent can distinguish the two without opening schemas.

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?

Gives clear when-not guidance (nuclei templates go to get_cve_details) and an interpretation rule for empty results, which prevents a false negative conclusion. It does not address when to prefer this over search_cve or get_vulnerability_snapshot, so it stops short of full routing guidance.

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