sodax_get_money_market_assets

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, establishing a safe read operation. The description adds 'all assets' which slightly conflicts with the openWorldHint (suggesting the list may not be exhaustive), but no additional behavioral details like pagination or data completeness are provided. The description adds minimal value beyond 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 a single, concise sentence that directly states the tool's action and scope. No unnecessary words or duplication of schema information.

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 lacks details about the output structure (e.g., asset addresses, symbols, rates). Without an output schema, the agent is left guessing what fields are returned. Sibling tools suggest similar outputs, but this is not conveyed. The description is incomplete for effective use.

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 coverage is 100% with both 'format' and 'chainId' documented. The description does not add any parameter-specific meaning beyond what the schema already provides. The baseline of 3 is appropriate given high schema coverage.

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 uses a specific verb 'List' and clearly identifies the resource as 'all assets available for lending and borrowing in the SODAX money market'. It effectively distinguishes from siblings like 'sodax_get_money_market_asset' (singular) and 'sodax_get_hub_assets' by specifying the money market context.

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 provides no guidance on when to use this tool versus alternatives such as 'sodax_get_money_market_asset' for a specific asset or 'sodax_get_hub_assets' for hub-specific assets. There is no mention of prerequisites or scenarios that favor this tool over others.

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