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

Annotations already establish readOnlyHint/idempotentHint/destructiveHint=false, so the safety profile is covered. The description adds real behavioral value beyond that: results come live from the mirror node, only successful calls are included, marketplace purchases are folded in, and the related_party operator-volume semantics are explained as 'labeled, not hidden'. Return fields beyond related_party are still unspecified.

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?

Two tightly written sentences that front-load the core action and scope; the contract ID and ordering are given up front. It is dense with useful parenthetical detail rather than padded, though the related_party clause makes the second sentence slightly heavy.

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 output schema, the description does carry the burden of return-value context and partially meets it by explaining the related_party flag semantics and the operator-volume labeling. It stops short of describing other return fields (amount, payer, timestamp) or pagination/limit behavior, so it is strong but not fully 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% and the single 'limit' parameter (1-25, default 10) is fully documented in the schema. The description adds nothing about the parameter beyond what the schema provides, so the baseline 3 is appropriate.

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 verb ('List'), a precise resource (successful contract calls on the Voicescape Tips contract 0.0.10854060), and the scope (tips plus marketplace purchases, most recent first). It clearly separates itself from siblings like verify_tip, quote_tip, and list_tip_assets by describing live read-only listing of recent activity.

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 — an agent understands this is for inspecting recent tip activity — but there is no explicit when-to-use/when-not guidance and no routing to siblings such as verify_tip or list_tip_assets. The 'read live from the mirror node' note adds useful context but does not tell the agent when to prefer this tool over alternatives.

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