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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: it discloses the measurement unit (documents, not deals), the absence of deal values or multiples, that controls are validated first, that a failed control refuses the call without charge, and that results carry a run id, date and citation line. The payment mechanics (payment_url, 402, per-run price, charge only on sound result) are also spelled out, which is exactly the kind of operational detail annotations cannot carry.

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?

It is front-loaded correctly: the trigger conditions come first and the caveats and mechanics follow. The pricing information is however stated twice in overlapping form ('charges nothing' then '$0.05 per run over x402 ... or $0.50 over MPP'), and the sample-URL sentence sits oddly at the end, so a trim would help.

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 must convey what comes back, and it does: quarterly series, direction, cross-check, filers with linked filings, plus run id/date/citation and explicit limits (no values or multiples). For a read-only tool with four optional, fully documented parameters, the only missing piece is any sense of result size or latency.

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 100% and each of the four parameters is documented in the schema itself (sic, phrase, sector enum, quarters with defaults and bounds), so the baseline is 3. The prose adds a little — the mutex between sector and phrase and the cross-check role of sic — but mostly restates what the schema already says. The mention of publish/question is for the payment POST body, not this tool's parameters, so it adds no parameter meaning here.

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 names a specific verb and resource set — M&A activity, deal flow, consolidation, active acquirers — and then precisely enumerates the return: the quarterly share of 8-K merger-agreement documents mentioning the sector, its direction, an industry-code cross-check, and top filers. It also explicitly bounds the measure ('counts documents, not deals') so an agent can tell it apart from a valuation or deal-database tool.

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?

The opening 'Use when the user asks about...' clause gives concrete trigger questions (is now a good time to buy/sell, who the active acquirers are), which is strong when-to-use guidance. It stops short of naming a sibling alternative or a when-not-to-use condition — no statement like 'for filing-volume trends generally use run_filing_trend' — so routing among the many run_* siblings is still partly inferred.

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