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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds a useful clarification that it does not spend credits (meaningful in a wallet context), but otherwise largely restates the annotation profile without covering pagination or response shape.

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 first two sentences are redundant ("List wallet transactions" and "List wallet transaction history"), diluting the front-loaded clarity. Short overall, but a sentence could be merged without losing information.

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?

Annotations cover the safety profile and the nested schema documents all filters, so little is missing for a read-only list tool. Return format and pagination behavior are undocumented, but no output schema exists to carry that, so a small gap remains.

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?

The schema's nested query fields (page, type, per_page, campaign_id, reference_type) each carry descriptions, even though top-level coverage reports 0%. The description adds nothing beyond 'optional filtering', so the schema does the heavy lifting — baseline 3.

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 wallet transactions" plus "transaction history with optional filtering." Clear for an agent, though it does not distinguish itself from siblings like dealmachine_get_mail_wallet_balance or dealmachine_get_mail_wallet_pricing.

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?

"with optional filtering" implies the tool's scope but gives no guidance on when to use it versus viewing balance/pricing, and no exclusions or prerequisites. Usage is only implied.

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