inscriptions_block_page_get

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

No annotations are provided, so the description carries the full burden. It mentions pagination and block height but does not disclose behaviors like ordering, default page size, error handling for invalid page numbers, or rate limits. Minimal transparency.

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 sentences: first states the action, second provides usage guidance. No fluff, front-loaded, and every sentence is essential.

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?

Given the tool's simplicity (2 numeric params, no output schema, no annotations), the description is fairly complete. It covers what it does and when to use it. However, it omits details like default page numbering or return format. Since no output schema, a hint about the return structure would be helpful.

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 has 0% description coverage for parameters. The description adds context by naming 'block_height' as the specific block and 'page' for pagination, but provides no additional constraints or formatting details beyond the schema's type definition. Some value added but not fully compensating for the lack of schema descriptions.

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 the action 'Get' and resource 'a specific page of Bitcoin Ordinals inscriptions in a particular block'. It distinguishes from siblings like 'inscriptions_block_get' (likely returns all inscriptions in a block) and 'inscriptions_page_get' (likely global pagination), specifying pagination and block height.

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?

Explicitly says 'Use this for paginated access to the inscriptions created in a specific block height', implying when to use. However, it does not mention when not to use it or explicitly suggest alternatives, though the sibling names provide context.

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