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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered. The description contributes one genuinely useful behavioral constraint: results are limited to legacy P2PKH addresses, so agents know other address types are excluded. However, it never says how the wallet is resolved in a zero-parameter tool (connected wallet, session context, or API key), which is the most important behavioral question here.

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?

A single dense sentence, front-loaded with the verb and scope, ending with the returned metadata. Efficient with no filler, though the long enumeration list makes it slightly heavy to parse.

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 does carry the return-value burden and it lists the asset classes and their metadata fields competently. The gap is the zero-parameter invocation model: it never explains that the target wallet comes from ambient context, leaving an agent unsure whether it must supply a wallet some other way before calling.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate. The baseline of 4 applies; the enumerated return fields (asset name, supply, divisibility) add context but are not parameter semantics.

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 ('Return') and a precisely scoped resource: legacy P2PKH Bitcoin wallet holdings on the Counterparty layer, then enumerates the asset classes returned (XCP, named Counterparty assets, Bitcoin Stamps, rare pepes). The combination of address-type scope plus Counterparty-layer scope distinguishes it from getBTCBalances, getRuneBalances, and getStampsByAddress without needing to name them.

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?

There is no when-to-use or when-not-to-use guidance. The returned asset classes overlap heavily with siblings like getStampsByAddress, getRareSats, and getBTCBalances, and the description never resolves which tool an agent should pick for a given question.

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