explorer_get_nft_inventory

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only safety is clear. The description adds minimal context about the output (collections and token IDs) but does not disclose pagination behavior, ordering, or potential limitations despite having page/pageSize parameters.

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 a single, front-loaded sentence with no filler. It conveys the core purpose efficiently, earning a high score for conciseness.

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 list tool with good schema coverage and annotations, the description is nearly sufficient. However, it omits any mention of return format or pagination behavior (e.g., default page size), which would be useful given the absence of an output schema. Still, the tool's simplicity and the rich schema keep it adequately complete.

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 all four parameters (address, chainId, page, pageSize) described in the schema. The tool description does not add any parameter semantics beyond what the schema already documents, so a baseline score of 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?

The description 'List NFT collections and token IDs owned by an address' uses a specific verb and resource, clearly indicating the tool's scope. It does not explicitly name sibling tools like explorer_get_nft_transfers, but the 'owned by an address' phrasing distinguishes it from transfer-history tools.

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 is provided on when to use this tool versus alternatives such as explorer_get_nft_transfers or evm_get_nft_info. The description simply states what it does without contextual or exclusionary hints.

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