sodax_get_money_market_reserve_assets

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

Annotations already indicate safe read (readOnlyHint=true) and non-destructive operation. Description adds 'used as collateral backing' context but does not disclose additional behaviors like authentication or rate limits. Adequate but not rich. Score 3.

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?

Single sentence is extremely concise and front-loaded with the action. No wasted words. Score 5.

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 one optional parameter and no output schema, description is minimal. It clarifies the purpose but does not explain return structure or potential missing data (openWorldHint). Adequate but could be more helpful. Score 3.

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 has 100% coverage with description for the single parameter 'format', so baseline is 3. Description adds no new meaning beyond what the schema's param description already provides. Score 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?

Description clearly states verb 'Get' and resource 'money market reserve assets' used as collateral. The name distinguishes it from siblings like sodax_get_money_market_assets and sodax_get_money_market_asset, but no explicit differentiation is provided. Score 4.

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 alternative money market tools or on choosing response format. Agent is left to infer usage from name alone. Score 2.

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