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

Annotations already declare this as a safe, read-only, idempotent operation. The description adds useful content-level context by naming edge cases like a proposed or in-force write-off, a pool with no data, and whether the price has started, but it does not clearly describe the response structure or how the different data groups are organized.

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 description is a dense, run-on enumeration mixing mechanism explanation, market fields, price-feed details, gas-station rules, and pre-market notes. The core purpose is buried rather than front-loaded, and the colon-separated lists make it hard to scan.

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 parameters and no output schema, the description carries the full burden of explaining what comes back. It does enumerate many returned data points and edge cases, but the presentation is opaque and does not clearly separate markets, prices, pool state, contracts, and gas stations into a coherent return model.

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?

This tool takes no parameters, so there are no parameter semantics to document. The baseline for zero parameters is 4, and nothing in the description needs to compensate for a schema gap.

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 domain resource (markets for agent credit lines) and hints at returned fields, but never states a clear action like 'list' or 'returns'. The opening sentence explains the broader Agent Credit Lines mechanism before getting to the markets payload, leaving the tool's exact purpose somewhat 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?

There is no explicit guidance on when to use this tool versus siblings such as markets, credit_line, credit_guardrails, or credit_gas. The phrase 'Before the market is on chain' implies a temporal use case, but no conditions, alternatives, or exclusions are stated.

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