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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds genuinely new behavioral context: it discloses the decoded semantic fields returned (likely change, address-poisoning warning), which an agent cannot infer from the annotations or a one-string schema.

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 sentence, front-loaded with the core idea ('A Dogecoin transaction in plain English') followed by an enumeration of what is returned. The list is somewhat long but each item is a real output field, so little is wasted.

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 carries the return-value burden and does so by enumerating the decoded fields, including the non-obvious address-poisoning warning. For a single-parameter read tool it is essentially complete, lacking only edge-case behavior for unknown txids.

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?

There is a single parameter with 100% schema description coverage including a regex pattern, so the schema fully carries parameter meaning. The description adds nothing about the txid beyond implying it identifies a transaction, matching the baseline for fully documented params.

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?

Names the resource (a Dogecoin transaction) and specifies exactly what is produced: payer/payee, amount, change, fee, confirmations, inputs/outputs, plus a poisoning warning. It is clearly the single-transaction explainer among siblings, though it does not explicitly contrast itself with find or get_block.

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 by the required txid parameter — call it when you already have a 64-hex transaction id. There is no explicit when-to-use or when-to-use-something-else guidance, and no mention of the sibling 'find' as the alternative for looking a txid up.

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