solanaGetAssetsByGroup

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states 'Get all assets' implying a read operation, but omits details on pagination behavior, rate limits, or potential performance implications. The agent is not informed that results are paginated or that 'all assets' may require multiple requests.

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 sentence with a useful example, making it highly concise and front-loaded. No wasted words, though it could include one more sentence on pagination without losing conciseness.

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 8 parameters including pagination (limit, page, before, after) and sorting (sortBy), and no output schema, the description fails to explain how 'all assets' are retrieved (e.g., pagination requirements) or what the return structure looks like. This is insufficient for an agent to use the tool correctly without external knowledge.

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%, with each parameter already explained (e.g., groupKey, groupValue, limit, page). The description adds no extra semantic value beyond the schema. According to guidelines, high coverage yields baseline 3.

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 action (Get) and resource (Solana assets in a specific group) with a concrete example (NFT collection), distinguishing it from sibling tools by group focus. However, it does not define 'group' explicitly; the schema fills this gap with groupKey and groupValue.

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 closely related siblings like solanaGetAssetsByAuthority, solanaGetAssetsByCreator, or solanaGetAssets. The description provides no context for selection, leaving the agent without clear decision criteria.

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