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

With no annotations provided, the description carries the behavioral burden well: it discloses that the tool is read-only, that chain ingest writes the deposits, how statuses behave, that unattributed deposits are held, the 1 CRD cost per call including rejected calls, the 404 behavior, and request_id support escalation. It stops short of fully covering auth/rate-limit behavior, but the schema covers api_key and x402 details.

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 front-loaded with the core purpose and then supplies error and cost details. The status enumeration is dense but each status meaning is useful; there is little wasted wording.

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?

For a 10-parameter read-only listing tool without annotations or an output schema, the description covers the main behavioral risks: cost, errors, status semantics, and the read-only nature. Pagination and result shape are left to the schema or omitted, but overall it is complete enough to invoke 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?

Schema coverage is already 90%, so the baseline is 3. The description adds meaningful semantics beyond the schema by explaining the status values, the unattributed-deposit behavior, the 404 for unknown user filters, and the per-call cost.

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 states a specific verb and resource: list on-chain token deposits for the project, newest first. It is clear and scope-specific, but it does not explicitly differentiate from related siblings such as get_transactions or list_x402_receipts.

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 implied by the tool purpose and the status explanations, and the read-only note helps. However, there is no explicit guidance on when to choose this over get_transactions, list_x402_receipts, or other transaction-oriented tools.

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