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

Annotations cover the safety profile (readOnly/idempotent/non-destructive), and the description adds substantial behavioral context beyond them: it decodes the on-chain TipSent event, exposes operator/self-directed tips via related_party rather than hiding them, and explicitly guarantees that a Tips-contract call without a TipSent event is reported as not-a-tip instead of a fabricated split. This is exactly the kind of edge-case and non-fabrication disclosure that annotations cannot carry.

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?

One dense but front-loaded paragraph: purpose first, then accepted formats, then return fields and the not-a-tip edge case. Every sentence earns its place, though the packing of formats, returns, and edge cases into one block is 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 must describe return values, and it does: sender_account (with the guidance to compare on it) and related_party. Combined with input formats and edge-case behavior, nothing an agent needs to invoke and interpret the result correctly is missing.

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% for the single parameter, so the schema already documents transaction_id, but the description adds meaning the schema lacks by enumerating accepted input forms (0.0.x@seconds.nanos, 0.0.x-seconds-nanos, and 0x EVM hash), which directly affects how the agent should format the argument.

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 precise verb+resource+scope: verifying a Hedera transaction against the Voicescape Tips contract, decoding the TipSent event into the 98/2 split. This is specific enough that an agent can distinguish it from siblings like prepare_tip, quote_tip, and recent_tips without opening any schema.

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 implies usage ('Verify a Hedera transaction...') and gives one actionable instruction ('compare payers on sender_account, not on EVM strings'), but it never explicitly says when to reach for this versus quote_tip, recent_tips, or verify_purchase, nor states prerequisites for obtaining a transaction_id. Usage is inferable but not spelled out.

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