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

Annotations already cover the read-only/idempotent/no-destructive safety profile, yet the description adds substantial behavior: it confirms call target and consensus success, decodes the on-chain TipSent event, reports the exact 98/2 split, and specifies the not-a-tip fallback instead of fabricating a split. That last disclosure is exactly the kind of behavioral guarantee an agent needs.

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?

Four sentences, each front-loaded with a distinct fact (purpose/contract, decode behavior, accepted formats, negative case) and zero filler. Nothing is redundant or padding.

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?

There is no output schema, so the description must explain what is returned, and it does: a decoded 98/2 creator/treasury split or an explicit not-a-tip result. Combined with the read-only annotations and full schema coverage, nothing an agent needs to invoke and interpret this 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%, so the schema already documents the single transaction_id parameter (baseline 3). The description earns above baseline by noting it accepts two id forms, 0.0.x@seconds.nanos and 0.0.x-seconds-nanos, which the schema example does not show.

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 (verify) plus resource (a Hedera transaction), and pins the exact contract (0.0.10854060) and what is being confirmed. The scope is unambiguous and clearly distinct from sibling tools like recent_tips or treasury_stats.

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 establishes clear context: this is for confirming whether a given transaction is a Tips-contract tip, and it explicitly defines the negative case (a Tips-contract call without a TipSent event is reported as not-a-tip). It does not name an alternative tool or state when to prefer it over recent_tips, so no explicit routing guidance.

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