das_searchAssets

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

No annotations provided. The description does not disclose behavioral traits such as pagination behavior, rate limits, whether it uses the DAS API directly, or any side effects. It only mentions 'flexible filters' without elaborating on what that entails.

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 very short (8 words) but this is due to underspecification rather than efficient communication. It lacks needed detail, so it is not appropriately sized.

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 9 parameters, no required fields, no output schema, and many sibling tools, the description is severely incomplete. It fails to explain pagination, the effect of filters, or how to combine them. The agent cannot infer correct usage without additional context.

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 only 33% (only 3 of 9 parameters have descriptions). The description adds no further detail beyond the schema. It does not explain the meaning of 'page', 'limit', 'burnt', 'frozen', 'compressed', or 'jsonUri' filters, leaving the agent to guess.

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 searches NFTs/assets with flexible filters via DAS. The verb 'search' and resource 'NFTs/assets' are specific. It distinguishes from single-asset retrieval tools like das_getAsset, but is somewhat generic compared to other das_* tools that specify filters like by owner or collection.

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 such as das_getAssetsByOwner, das_getAssetsByCollection, or das_getAsset. The description does not mention when not to use it or provide any context for selection among siblings.

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