Ordiscan: getAlkaneAddressUTXOs

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true, so the tool's safety profile is clear. The description adds context about the content of UTXOs (tokens, NFTs, etc.), which provides useful behavioral detail beyond annotations.

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?

Single sentence, perfectly sized, front-loaded with verb and resource. No wasted words, every part adds value.

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?

For a simple read tool with no output schema, the description sufficiently explains what the tool returns. It could mention data format or limitations, but the inclusion of token types adds completeness. The tool's low complexity makes this adequate.

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 description coverage is 100% with clear description for the single parameter 'bitcoinAddress'. The description adds no additional meaning beyond what the schema and name imply, so baseline 3 is appropriate.

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?

Description clearly states 'Get the UTXOs for a given Bitcoin address' with a specific verb and resource. It adds scope by mentioning inclusion of tokens, NFTs, contracts, etc., distinguishing it from sibling tools like getAlkaneAddressBalance or getUtxoRunes.

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?

No explicit guidance on when to use this tool vs alternatives. Usage is implied by the description, but no when-not or alternative tool references are provided. Siblings exist for related functions, but differentiation is not stated.

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