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

With only readOnlyHint available, the description carries the burden and delivers well beyond it: explicit return shape, units (whole USD vs ratio, '0.92 means 0.92x'), interpretation rule (under 1.0 = dividend partly funded from capital), missing-input policy (null, named, never zero), a refusal error code (DATA_UNAVAILABLE), and the internally-managed BDC edge case.

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?

Dense but front-loaded: the scope constraint and return shape come first, then the semantics of the ratio, then failure modes and caveats. Nearly every clause carries operational value, though the source/licensing sentence is the least essential.

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, so the description must explain returns — and it does, enumerating every returned key with its units and interpretation while covering error, null, and edge-case behavior. Nothing needed to call or interpret the tool 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?

Single parameter with 100% schema coverage, so the schema already documents the ticker and its examples. The description adds no parameter-specific syntax or format guidance, making the baseline 3 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 resource (BDC fee load + NII-based dividend coverage) with an explicit scope qualifier ('ONE fiscal year (not a series)'), which immediately separates it from time-series siblings. An agent can identify the exact artifact produced without opening the 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?

Gives clear context for when the tool applies: single fiscal year rather than a series, one BDC issuer, SEC EDGAR Statement-of-Operations filing data rather than a vendor feed. It does not name an alternative sibling or state exclusions, so it stops short of the top band.

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