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

Exceptional disclosure beyond the readOnlyHint annotation: missing inputs are returned as named nulls (never zero), unreachable stores are refused with DATA_UNAVAILABLE, internally-managed BDCs carry no fee lines by construction, and the data source (SEC EDGAR 10-K/10-Q XBRL, not a vendor feed) plus free/caveat behavior are all stated. Consistent with readOnlyHint=true.

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?

Front-loaded with the core purpose and return shape, then caveats. It is dense and semi-colon packed, but nearly every clause conveys a distinct fact an agent needs (units, ratio interpretation, null/refusal semantics, source). Minor cost in readability, not waste.

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?

No output schema exists, and the description fully carries that burden: it enumerates the return keys, states units (whole USD), explains the dividend_coverage ratio interpretation (<1.0 means capital-funded), and flags what is NOT returned (fee rates, dividend amount). Nothing needed to call or interpret it is missing.

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 parameter and schema coverage is 100%, so the schema already fully documents 'ticker'. The description adds no syntax or format detail beyond confirming it is a BDC ticker, so 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 ('BDC fee load + NII-based dividend coverage') and explicitly scopes it to ONE fiscal year rather than a series, which distinguishes it from the sibling time-series tools like ol_bdc_credit_quality or ol_bdc_mark_changes. The return field list confirms exactly what it produces.

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 clarifies scope constraints (single fiscal year, not a series) and notes the internally-managed BDC edge case, but never names an alternative tool or states the conditions under which an agent should prefer this over other BDC tools in the sibling set. Usage is implied rather than routed.

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