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

No annotations are provided, so the description carries the disclosure burden, and it does more than most: it enumerates the payload fields (title/name, description, source and maturity, targeted CVEs) in the absence of an output schema. It does not mention permissions, rate limits, or behavior on a non-existent identifier, which keeps it from a 5.

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, each with a distinct job: what it does, what it returns, and where to go instead. The core action and return contents are front-loaded before the routing guidance.

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 one-parameter read tool with no output schema, the description covers action, accepted identifiers, return fields, and sibling alternatives. An agent has everything needed to select and invoke it correctly without further context.

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% and the single parameter is documented in the schema as 'a UUID or a CVE ID'. The description restates the same accepted identifier forms without adding syntax, format constraints, or fallback behavior, so the schema is doing the semantic work.

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 ('Fetch a single Mallory exploit by identifier') and immediately enumerates what is returned, so the agent knows exactly what it gets. It explicitly distinguishes itself from sibling listExploits (lookup vs. discovery) and queryApi (single-entity vs. pivots).

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?

Names both the precondition and the alternative: 'If you only have a name or search terms, call listExploits first to find the exact identifier', and routes relationship/cross-entity work to queryApi. The when-to-use and when-not-to-use conditions are both explicit.

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