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 context beyond them: the three checks performed, the SHA256 report hash, and critically that it returns a prepared *unsigned* HCS transaction the caller must sign with their own payer and submit. This discloses the read-then-sign side effect that annotations alone would not reveal.

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?

Front-loaded with the verdict and checks, and information-dense for a complex tool. Slightly verbose in restating the unsigned/signing point ('unsigned, so the caller sets their own payer and submits' partially duplicates the earlier clause), keeping it short of a 5.

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?

No output schema exists, so the description carries the return-value burden and does so well: verdict values, evidence source (mirror node), report hash, and the prepared transaction. It omits how 'insufficient_data' is triggered and any rate/pagination 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?

With a single parameter at 100% schema description coverage, the schema already documents the 'subject' account id. The description's 'Pass a 0.0.x account id' restates the schema's example without adding format or validation detail, so baseline 3 applies.

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 ('return a deterministic verdict over a Hedera agent's on-chain tipping behavior') and names the exact output values (clean / flagged / insufficient_data). An agent can distinguish it from siblings like verify_tip or recent_tips without opening the 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?

Usage is only implied: it explains the sign-and-submit workflow for the returned attestation transaction and closes with 'Pass a 0.0.x account id.' There is no explicit when-to-use versus alternatives (e.g. verify_tip, recent_tips) and no stated exclusions or preconditions.

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