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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds real context: the source (each Q3 10-Q on EDGAR), the freshness (the day it is filed), the ordering (biggest cut first), and the paywall mechanics (top 10 free, $0.25 via x402/USDC on Base or a Tensorust key). There is a mild tension with openWorldHint=false given the live external EDGAR feed, though the result set is bounded enough that it does not read as a flat contradiction. What it omits is the record shape — fields per cut/holder — which matters for a paid, metered call.

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?

Two sentences, front-loaded with the earnings-season hook and the cut definition before the pricing clause. The free-vs-paid detail is repeated between description and schema, and the second sentence is dense, but nothing is filler.

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 describing returns and does so reasonably: cuts ranked biggest-first, pending holders flagged as likely next markdowns, and the top-10 free cap implying truncation behavior. A per-record field list or an explicit note that results are current-as-of-latest-filings would close the remaining gap.

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?

Only one optional boolean parameter, and its schema description already states the full=true expansion plus the $0.25/x402 pricing and key alternative. The prose restates that tradeoff and adds 'every pending holder,' which is a marginal gain over the schema. With 100% coverage the baseline of 3 is appropriate.

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 precise verb and resource: BDC funds that cut a first-lien loan's mark by 5+ points between Jun 30 and Sep 30 2026, sourced from Q3 10-Qs on EDGAR. That scope is narrow enough to distinguish it from siblings like lender_marks or credit_disagreements without opening any schema.

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 clear situational context — 'Live through earnings season' — and explains the free-versus-follow-up use case via the pending-holder angle, which tells the agent what question this answers. It never explicitly excludes or routes to sibling tools, so it stops short of full when/when-not guidance.

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