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

Annotations only declare readOnlyHint=true, but the description adds substantial behavioral context: matcher-verified only at >=0.9 confidence, headline+link only with NO provider summary so false attribution cannot surface, empty-result semantics, REFUSED/DATA_UNAVAILABLE on unreachable store, and free/source provenance. This is genuinely beyond what structured fields convey.

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?

Purpose and the framing question are front-loaded, and virtually every clause carries load-bearing information (confidence threshold, caps, absence semantics). It is dense with em dashes and caps, bordering on run-on, but there is little true filler to cut.

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?

Although there is no output schema, the description fully specifies the return envelope {summary, count, items} and each item's fields {borrower, headline, source, url, date}. Combined with the caps and failure-mode notes, an agent has everything needed to call and interpret the tool.

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 parameter already documents its default and hard cap. The description merely restates the same defaults/caps (limit 25/100, since_days 7/90, min_holders 2/50), adding no syntax or interpretation beyond the schema. Baseline 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?

States a specific verb+resource+scope: recent VERIFIED news for private-credit borrowers held across MULTIPLE BDCs. It even supplies the natural-language question it answers ('what broke recently for the cross-BDC borrowers I should watch?'), which cleanly separates it from generic siblings like get_news, search_news_archive and search_bdc_borrower.

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?

Gives clear context for when to use it (cross-BDC borrower pulse) and an important exclusion-style note that empty results are 'absence, not a signal'. It does not, however, name an explicit alternative (e.g. get_news or search_news_archive) or state when NOT to use this tool, so it stops short of a 5.

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