das_getAssetsByOwner

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

With no annotations and no output schema, the description only mentions pagination but does not disclose other behaviors (e.g., sorting, default limit, read-only nature, or any destructive effects). The 'supports pagination' hint is insufficient.

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 single sentence is very concise but too brief for a tool with 6 parameters—fails to earn its place by omitting crucial details.

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?

No output schema and no description of return format, error handling, or pagination details. The description is incomplete for an agent to reliably use the tool.

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 low (17% with only ownerAddress described). The description adds no parameter details beyond 'pagination', leaving page, after, limit, before, and sortBy unexplained, which the schema also fails to describe.

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 tool gets NFTs/assets owned by a wallet (specific verb+resource) and mentions DAS and pagination support, distinguishing it from siblings like das_getAssetsByCollection or das_getAssetsByCreator.

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 (e.g., das_searchAssets for broader searches), no prerequisites or exclusions, and no context on required permissions or wallet format beyond the schema.

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