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

Annotations already indicate readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds only domain context ('used as collateral backing') and does not disclose additional behavioral traits such as response format, pagination, or rate limits. Since annotations cover the basics, the description is minimally sufficient.

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, front-loaded sentence with no filler words. It is appropriately concise, though slightly terse and could have benefited from one additional clause about output context.

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?

For a simple one-parameter read-only tool with good annotations and schema coverage, the description provides the core action. However, it does not explain what the returned assets look like or how they relate to other money market concepts, and there is no output schema to compensate. It is minimally adequate but leaves some ambiguity.

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?

The only parameter 'format' is fully described in the schema with enum values and a clear explanation ('json' vs 'markdown'). The tool description adds no extra parameter semantics, so the baseline of 3 applies due to 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 clearly states the tool retrieves 'money market reserve assets used as collateral backing', using a specific verb and resource. It distinguishes from sibling tools like sodax_get_money_market_assets by the 'reserve assets' and 'collateral backing' qualifiers, though it doesn't explicitly differentiate in a contrastive way.

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 explicit guidance on when to use this tool versus alternatives, nor does it mention conditions, exclusions, or related tools. Sibling tools are numerous, but no context is given for selecting this one.

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