Ordiscan: getInscriptionActivity

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

Annotations already indicate readOnly, destructive false, idempotent, and openWorld. Description adds no behavioral context beyond 'get', such as response size, pagination behavior, or error cases. The page parameter is not explained.

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, no fluff. Every word carries meaning. Efficient for the minimal information provided.

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?

Despite rich annotations, the description is too sparse. It does not define 'inscription activity', fails to address the page parameter for pagination, and does not set context relative to many sibling tools covering similar domains.

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. The description mentions 'given address' but does not explain the format or constraints for bitcoinAddress, and ignores the optional page parameter entirely. No added value over parameter names.

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 the action ('get') and the resource ('inscription activity') for a given address. It distinguishes itself from sibling tools like getInscriptionInfo and getInscriptionsByAddress by focusing on 'activity', but lacks definition of what activity entails.

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 guidance on when to use this tool versus alternatives. Does not mention prerequisites, limitations, or contrast with similar tools like getBRC20Activity or getRunesActivity.

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