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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds value by detailing the read/discovery workflow, pricing model, and signer boundary (e.g., 'hosted reads/builders never receive keypair bytes'), providing transparency beyond the annotations.

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 verbose and contains redundant SAP boilerplate that is also repeated in the input schema description. The core purpose is concise, but the overall text is long and unfocused, which detracts from clarity.

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?

With an output schema present, the burden on the description is reduced. However, the description does not explain what the tool returns (e.g., structure of assets) and instead fills space with SAP context. It is adequate but not fully complete.

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?

Input schema coverage is 100%, but the descriptions are tautological (e.g., 'Page pagination control for Das Get Assets By Collection') and the collectionAddress description is misleading ('NFT mint address'). No additional meaning beyond the schema is provided; in fact, it introduces inaccuracy.

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 states 'Get all NFTs in a collection via DAS' which is clear, but then expands to 'by owner, creator, collection, or search query', conflating this tool with siblings that are specifically for those other query types. The parameter description for collectionAddress incorrectly labels it as an 'NFT mint address' rather than a collection address, reducing clarity.

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 advises to use for read-only discovery and to prefer DAS reads over Metaplex writes, which is helpful. However, it does not explicitly distinguish when to use this tool versus the similar siblings (das_getAssetsByOwner, etc.), and the SAP-specific pricing and routing guidance, while possibly useful, is not typical usage guidance.

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