solanaGetAssets

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only states the tool's basic function without detailing any side effects, rate limits, or data completeness. For a read operation, this is minimal but acceptable; however, more specifics (e.g., 'returns basic metadata, not full on-chain data') would improve transparency.

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 a single, efficient sentence that conveys the core functionality without redundancy. Every word serves a purpose, making it easy to parse quickly.

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?

The description is adequate for a simple batch getter tool with a clear schema, but it lacks details about what 'detailed information' includes (e.g., metadata, supply, owners). No output schema is provided, so the description could clarify the return format. Overall, it is minimally complete but could be improved.

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% with both parameters described. The description adds no additional parameter meaning beyond restating the overall purpose. Baseline score of 3 is appropriate as the schema already documents the parameters sufficiently.

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's function: 'Get detailed information about multiple Solana assets by their mint IDs in a single request'. It specifies the resource (Solana assets), action (get), and criteria (by mint IDs, multiple in one request), distinguishing it from sibling tools like solanaGetAsset (single asset) and solanaGetAssetsBy* (other criteria).

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 implies usage context by mentioning 'multiple' and 'single request', indicating this is for batching queries. However, it does not explicitly state when not to use it or name alternatives. The context is clear enough for common use cases, but lacks exclusions.

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