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

Beyond the readOnlyHint annotation, the description discloses the default limit (25), hard cap (100), absence of pagination offset, that the response shape changes with the arguments, that 'sentiment' is a label not a number, that matching is prefix-word rather than semantic, and that a configured API key is required. This is unusually rich behavioral context.

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, with scope first and the crucial response-shape warning capitalized for emphasis. The all-caps sentences are justified by the risk they flag, though the description is on the longer side.

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 return-value burden and does so explicitly, documenting both possible shapes ({articles, total} vs {articles, count} with richer rows). For a read tool whose annotation already covers safety, nothing an agent needs to call it correctly 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?

Schema coverage is 100%, so baseline is 3, but the description adds genuinely new semantics: query matching is 'prefix-word, not semantic' and 'sentiment' is a label string. That goes beyond the schema text and materially affects how an agent builds a query.

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 and resource ('Read the Oxford Ledge news archive by ticker and/or keyword, newest first'), so an agent immediately knows what it does. It does not, however, differentiate itself from the sibling 'search_news_archive' or 'ol_bdc_borrower_news_today', leaving overlap ambiguous.

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 'by ticker and/or keyword' phrasing implies when the tool fits, but there is no explicit when-to-use versus the sibling 'search_news_archive', nor any exclusion. Usage is implied rather than stated.

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