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

Annotations already carry readOnly/idempotent/non-destructive, so the trailing 'Read-only' is redundant; however the description adds real context beyond the annotations – result ordering ('newest first'), what each row contains, and the negotiation mechanics that follow. It does not say whether the list is capped by total count or how pagination beyond 'limit' behaves.

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?

The purpose is front-loaded, but the sentence about backers offering with a LineOffer and owners accepting with pool consent describes a workflow rather than this read tool, and 'Read-only' merely repeats the annotation. The parenthetical field list is dense jargon that could be tightened.

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?

There is no output schema, so the description correctly carries the burden of describing return shape (request terms, agent's Priors record, offer count) and ordering. It leaves the total-count/pagination story implicit, but an agent has enough to call it correctly.

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 the schema already documents it fully (1-50, default 20). The description adds no meaning about 'limit' beyond the schema, so the baseline 3 applies.

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 ('List the open requests on Priors' line board') and enumerates the fields each entry carries (line in USDG, term in days, premium per 30 days, expiry, agent record, offer count). It also explicitly distinguishes itself from the sibling 'line_request', which 'gives one request'.

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?

Names the actor and situation ('a root's owner (a backer) looking for an agent to back') and outlines the follow-up path (offer with a signed LineOffer, owner accepts with pool consent). The single-record alternative is named, but there are no explicit when-not-to-use exclusions against other siblings such as line_options or agents_for_hire.

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