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

Annotations already establish readOnly, idempotent, and non-destructive behavior. The description adds valuable behavioral detail beyond that: completed amounts are grouped by asset and network, never combined or converted into fiat, and the result is not all-time revenue. These are meaningful caveats an agent needs before interpreting results. No contradiction with annotations.

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?

Three short sentences with no filler. The core action is front-loaded, followed by two high-value clarifications that prevent misinterpretation. Every sentence earns its place.

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?

The tool is simple, has an output schema, and annotations cover the safety profile. However, with 0% schema description coverage, the missing parameter semantics is a real gap: an agent cannot tell whether status defaults to COMPLETED or whether grouping changes when other statuses are requested. The description covers scope and currency-grouping caveats well but is not fully complete for selecting and using parameters 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 description coverage is 0%, so the description bears the burden of explaining page, limit, and status. It only hints at pagination with 'one page' and at status with 'Completed amounts', but it never explains how the optional status filter behaves, what the default is, or how limit/page interact. The parameter names and enum are self-evident, but the description adds almost no semantic value for the parameters.

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 clear verb-resource pair: 'Analyze one page of owned payments.' It adds specific scope (one page, owned payments) and explains the output shape (completed amounts grouped by asset and network). While it distinguishes itself from list/export tools, it doesn't explicitly differentiate from the similarly named 'auraspay_payments_report', so it stops short of a 5.

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?

The description gives useful context: it is for a single page, not all-time revenue. However, it never names alternatives or states when to prefer this over payments_list, payments_report, or payments_export_csv. The 'Not all-time revenue' line implies an exclusion but does not tell the agent which sibling to use instead.

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