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

With no annotations at all, the description carries the full burden and does real work: it states the data comes from public chain data, that the market is not operated by the tool provider and nothing is held (custody disclaimer), and that the operation is read only and free. It stops short of describing freshness, caching, or failure behavior for an external chain read.

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?

A single front-loaded sentence that opens with the owner and resource before listing fields. It is dense but every clause adds a distinct fact (chain, custody, field list, cost); the parenthetical aside could be split for readability but nothing is redundant.

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, yet the description enumerates the return payload (collateral, supplied/borrowed USDG, utilization, max LTV, tagged stock-token collateral), which is exactly what is needed to interpret results. What is missing is how the read behaves against a live external chain — staleness and error paths are unaddressed.

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?

The tool takes zero parameters, so the baseline is 4 and nothing needs explaining. The description instead spends its words on the payload fields, which is the right compensation for a parameterless tool.

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 specific resource (Longbow's lending markets and vault on Robinhood Chain) and enumerates the data returned — collateral, USDG supplied/borrowed, utilization, max LTV, stock-token tagging. It implicitly separates itself from the internal loan_* siblings by scoping to an external chain and USDG, though it never names an alternative explicitly.

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?

Usage is only implied: an agent can infer this is the tool for inspecting external Longbow market state, and 'Read only, free' signals it is safe to call casually. There is no explicit when-to-use, no exclusion of sibling loan tools, and no guidance on refreshing or how often to poll.

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