Das Get Assets By Owner

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive. Description adds context like 'Protocol das; operation class read' and 'supports pagination', enhancing transparency without contradiction.

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?

Four sentences, front-loaded with purpose. Could be slightly tighter by removing redundant usage guidance (third sentence partially repeats first). Still concise overall.

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?

Output schema exists, so return values are covered. Description covers purpose, protocol, pagination, and usage context. Missing details like sorting options are covered by schema. Sufficient for an agent to select and invoke.

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 baseline is 3. Description mentions 'supports pagination', which groups pagination parameters, but does not add meaning beyond schema details for individual parameters.

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?

Clearly states 'Get all NFTs/assets owned by a wallet via DAS (supports pagination)', with specific verb and resource. Distinguishes from sibling tools like das_getAsset (single asset), das_getAssetsByCreator, etc.

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?

Provides usage context: 'Use for read-only DAS NFT and asset discovery' and 'Prefer DAS reads before Metaplex writes'. However, the sentence 'by owner, creator, collection, or search query' is misleading as this tool is specifically by owner, not the other criteria covered by siblings.

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