Ordiscan: getInscriptionsByAddress

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds value by disclosing pagination and detailing the return fields (number, content type, traits, satpoint), without contradicting 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?

Two highly efficient sentences, front-loaded with the core purpose and a concise usage note. No redundant 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?

With no output schema, the description adequately explains the return structure (fully-detailed with specific fields) and mentions pagination. Could be improved by noting default page size or ordering, but it meets essential needs.

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 coverage is 100% and the description adds no additional meaning beyond what the schema already provides for the two parameters (bitcoinAddress and page).

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 'Return paginated, fully-detailed Bitcoin Ordinals inscriptions held by a given Bitcoin address' with a specific use case 'display a wallet's NFT-style holdings', effectively distinguishing it from siblings like getInscriptionInfo or getOwnedInscriptionIds.

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 provides explicit context for usage ('Use this to display a wallet's NFT-style holdings'), but lacks explicit when-not-to-use guidance or direct comparisons to alternatives, though the sibling list makes differentiation possible.

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