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

With no annotations at all, the description carries the full burden and does disclose non-obvious behavior: this is a paid, per-call metered vendor asset at $0.01 USDC, and the payment proof must travel in MCP request headers (X-Payment / X-Payment-Tx / Authorization: Bearer fg_…) rather than as a parameter — a real invocation pitfall. It also enumerates what the response contains. Gaps remain: no mention of pagination, default time window, rate limits, or maximum limit.

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 key content is front-loaded, but the text is bloated by full duplication of the vendor/pricing/args block in Chinese and English, and the Chinese half refers back to itself with "参数同左", adding length without adding information. A single compact block would convey the same thing at half the size.

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 six-parameter tool with no annotations and no output schema, the description does cover the return fields, the paid-auth mechanism and the parameter names, which is enough to attempt a call. It falls short on default behavior for optional parameters (all six are optional, all default null) and on how filters combine, so an agent must guess at what an unfiltered call returns.

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% across six parameters, so the description must supply meaning and it largely does not — it merely recites the parameter names (protocol, chain, classification, days, min_amount, limit) in both language blocks. No value formats, enum candidates for classification, units for min_amount, or default/range for days and limit are given, and the Chinese "参数同左" is circular.

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 and resource — return the full list of crypto hack events with date, protocol, attack type, amount, chain and repayment status, plus loss distribution by chain and year. The word "full" implicitly contrasts with the sibling exploit-alerts.hack_now, but it never names that sibling, so the differentiation is left to inference.

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?

It gives a sample user question ("what crypto hacks happened recently") which anchors when the tool is appropriate. However, it never says when to prefer exploit-alerts.hack_now (the obvious cheaper/quicker alternative) or when this full report is overkill, and it gives no exclusions.

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