solanaGetAssetsByAuthority

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

No annotations provided. The description claims 'Get all' but the schema includes pagination parameters (limit, page, before, after) with a max of 1000, implying paginated results not disclosed. No mention of side effects or network dependency.

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 and front-loads the main purpose efficiently. However, it could be slightly longer to clarify pagination behavior without becoming overly verbose.

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 7 parameters including nested objects (sortBy), pagination mechanics, and no output schema, the description is insufficient. It lacks details on pagination, sort options, and return structure, leaving significant gaps for an agent to use 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 100%, so the schema already documents each parameter's purpose. The description adds no additional meaning beyond what's in the schema, resulting in baseline score.

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), resource (Solana assets), and the filtering criterion (by authority address). It distinguishes from siblings like solanaGetAssetsByOwner or solanaGetAssetsByCreator, though it says 'all' while the schema implies pagination limits.

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 alternatives (e.g., solanaGetAssetsByOwner, solanaGetAssetsByCreator). The description does not mention any prerequisites or context for authority-based queries.

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