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

Annotations already establish this as a safe read (readOnlyHint=true, closed-world openWorldHint=false), so the bar is lower. The description adds genuine value by scoping the corpus to 'verified' incidents and disclosing the shape of what is returned (date, impact, users affected, loss, refund status, source URLs), which is important given there is no output schema.

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 definition is compact and front-loaded, leading with the resource and its contents before the optional filter. The field enumeration is dense but every item earns its place since there is no output schema to lean on.

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 carries the burden of explaining return values and does so thoroughly. The main gap is the absence of differentiation from search_scams and any note on result ordering/pagination, but overall it is sufficient to invoke 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 coverage is only 50%: the 'bot' slug parameter is documented in the schema, but 'limit' is undocumented there. The description clarifies that the bot filter is optional but adds no detail on ordering, defaulting, or what limit controls, so it only partially compensates for the coverage gap.

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 states a specific verb+resource: retrieving verified security incidents (hacks, exploits, key leaks) at trading bots, and enumerates the returned fields. It is clear what the tool returns, though it does not explicitly distinguish itself from the sibling search_scams, which likely covers a related but different (unverified scam) space.

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?

'Optionally filter by bot slug' implies one usage pattern, and 'verified' implies a quality boundary, but there is no explicit when-to-use vs. when-not-to-use guidance. Critically, it never says how this differs from search_scams, leaving the agent to infer the distinction between the two siblings.

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