Indexer: List NFT contract addresses by owner

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

Annotations already declare readOnlyHint and openWorldHint, so the description adds value by specifying the endpoint and pagination details (page/size/direction/cursor). It does not contradict annotations and provides extra behavioral context about the API-based nature of the tool.

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, no fluff. The description front-loads the main action ('Get all NFT contract addresses for a given owner') and then provides structured details. Every sentence earns its place.

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 6 parameters and existence of an output schema, the description is mostly complete. It covers the core purpose and key parameter groups. However, it could elaborate on the interplay between cursor and page-based pagination, but that is a minor gap. The output schema compensates for return format details.

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%, so the baseline is 3. The description briefly mentions 'address and pagination (page/size/direction or cursor),' but this adds minimal meaning beyond what the schema already provides. It does not clarify nuances like the relationship between cursor and page/size or the format of the 'owner' parameter.

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 NFT contract addresses for a given owner, with specific mention of the VeWorld Indexer and endpoint. The verb 'Get' and resource 'NFT contract addresses by owner' are explicit, and it distinguishes from sibling tools like 'getNFTs' which likely returns individual tokens.

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 tells the agent when to use it (for owner's NFT contract addresses) but does not explicitly mention when not to use it or point to alternative tools. For example, it could note that 'getNFTs' retrieves individual NFT tokens, while this tool lists contract addresses. The guidance is implicit but could be clearer.

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