Daily statement

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

Beyond the annotations, the description discloses important behavior: failed transactions are excluded, fees are counted only on outgoing transactions, staking rewards are included as income, staking contract movements are excluded, and missing prices return closeUsd: null instead of a guess. These details materially affect interpretation of the results.

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 layers in behavioral details in a logical order. It is somewhat dense but every sentence contributes to understanding the statement output.

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 read-only reporting tool with no output schema, the description covers pricing basis, inclusion/exclusion rules, and null handling well. It stops short of detailing the returned fields beyond closeUsd, but the behavioral picture is largely complete.

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 the schema already documents year, month, and address. The description adds useful context about UTC days and monthly granularity, but does not add parameter-specific meaning beyond the schema descriptions.

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: day-by-day money in/out for a year or month, priced at the CoinGecko daily close in USD. It also differentiates itself from general transaction listing by tying the output to the NimBooks tax statement basis.

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?

It implies the tool is for annual or monthly statement-style reporting (e.g. tax statement basis), but it does not explicitly name alternatives such as list_transactions or get_summary or state when not to use it. The usage context is clear but left implicit.

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