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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by enumerating what the record contains (metadata, ownership, royalty config, supply) and providing a concrete call example, without contradicting 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?

One dense, information-rich sentence followed by a concrete example. Every phrase contributes: resource, record type, fields returned, and call shape. No filler or redundancy.

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?

For a read-only single-asset lookup, the description is complete: both required parameters are documented and exemplified, the return content is described at field-group level, and annotations cover the safety profile. No output schema exists, but the description adequately bridges that gap.

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 100%, so both parameters are already documented. The description reinforces that id is the mint address and shows a realistic example, but it does not add meaningfully beyond the schema.

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 a specific resource (a Solana asset/mint) and a clear operation (return the full DAS record for a single token or NFT by mint address). It also distinguishes itself from the sibling helius_assets_by_owner by emphasizing single-asset lookup rather than owner-based listing.

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 context is clear: use this when you have a mint address and need complete DAS details for one asset. It does not explicitly name alternatives or say 'use helius_assets_by_owner instead for multiple assets,' but the single-vs-owner distinction is strongly implied.

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