Ordiscan: getAlkaneAddressUTXOs

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

Annotations already indicate it's a read-only, idempotent, non-destructive operation. The description adds context about the types of UTXOs included but does not mention any other behavioral aspects like pagination or rate limits.

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?

The description is extremely concise with two sentences that efficiently convey the tool's purpose and scope. No extraneous 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?

For a simple tool with one parameter and no output schema, the description adequately covers what it does. It could mention the response format or limitations, but is otherwise complete enough given the context.

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 single parameter 'bitcoinAddress' is described in both schema and description. Since schema coverage is 100%, the description does not add meaningful extra semantics beyond repeating the schema definition.

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?

The description clearly states it retrieves UTXOs for a given Bitcoin address, specifying it includes tokens, NFTs, contracts, and other alkanes. This distinguishes it from sibling tools like getAlkaneAddressBalance.

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?

The description implies the tool is for fetching UTXOs, but lacks explicit guidance on when to use it over alternatives or when not to use it. No comparison with sibling tools is provided.

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