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

With no annotations, the description carries the full burden, and it does meaningfully: it discloses that the response merges an indexer copy (which may be absent, 'if indexed') with an independently decoded on-chain payload, asserts chain-over-indexer precedence, and warns about untrusted free-text fields with explicit non-execution guidance. It still omits auth requirements, rate limits, and what happens when a txid is unknown, so it is strong but not complete.

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 purpose, followed by the provenance contrast and then the security caveat, in a logical order. It is a bit repetitive ('Chain is the truth; the indexer is a cache' restates the same point), but every sentence carries actionable information.

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 carry the return shape — it does, describing the two-part indexer/on-chain result — and it adds a real safety directive. The main gap is the behavior on an unindexed or unknown txid (error vs. partial result), which the 'if indexed' phrasing hints at but never resolves.

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?

Only one parameter, and schema description coverage is 100% with the format ('64-hex transaction id') already documented in the schema. The description adds the word 'by txid' but no format, validation, or edge-case semantics beyond what the schema provides, so the 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 precise verb+resource ('Get one pin by txid') and immediately differentiates itself from the sibling list_pins by specifying a single-pin, two-source retrieval. It also clarifies what the result contains (indexer copy plus independently decoded on-chain payload), so an agent knows exactly what it is selecting.

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 and the singular scope — call it when you have one transaction id and need that pin. However, it never says when to prefer this over list_pins, get_inscription, or global_activity, nor does it state any preconditions such as whether the txid must be an indexed pin.

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