das_getAssetsByCollection

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

With no annotations, the description must disclose behavioral traits. It implies read-only behavior but does not explicitly state it, nor does it mention pagination behavior, rate limits, or any side effects. The brevity leaves key safety and operational assumptions unaddressed.

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 extremely concise (6 words), which is efficient but compromises clarity. It is front-loaded with the core action, but lacks supporting details expected for a tool with multiple parameters and no output schema.

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 tool has three parameters, no output schema, and no annotations, the description is insufficient. It does not explain return format, pagination, or the meaning of 'via DAS'. An agent would need additional context to use it correctly.

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 low (33%)—only collectionAddress has a description. The tool description adds no parameter information beyond the schema. It does not explain page, limit, or collectionAddress semantics, leaving the agent to infer from parameter names alone.

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 retrieves all NFTs in a collection via DAS. The verb 'Get' and resource 'all NFTs in a collection' are explicit. Among sibling das_get* tools, the name and description sufficiently differentiate it by collection, though it does not explicitly distinguish from similar 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 like das_getAssetsByCreator or das_getAssetsByOwner. There is no mention of prerequisites, context, or when not to use it.

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