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

With no annotations present, the description carries the full burden and does a solid job: it discloses that approval is independent of risk assessment, that unassessed scores come back null, and it spells out the auth/payment model (0.001 USDC via x402 payment header, or free with an API key). These are non-obvious operational traits an agent could not infer from the schema.

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 core purpose and null-semantics warning are front-loaded, and the access/payment note is clearly bracketed off. Minor redundancy ('Approval is independent of risk assessment' partially overlaps the null warning) but nothing wasteful.

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 one-optional-param read tool with no output schema, the description covers purpose, return contents ('market metadata and risk scores'), null semantics, and the payment model. The only gap is the shape/fields of the returned metadata, but that is reasonable to omit without an output schema.

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?

Only one optional parameter (top_n) with 100% schema description coverage, so the schema already documents it fully. The description adds nothing about truncation ordering or defaults for top_n, so it sits at the baseline for high-coverage schemas.

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 opens with a specific verb+resource ('List assets approved by Mangrove') and scopes the content (supported stablecoins and tokens). It implicitly separates itself from the singular get_asset by framing this as an enumeration of the approved universe, though it never names a sibling explicitly.

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?

Usage is implied — call this to obtain the set of Mangrove-approved assets — but the description never says when to prefer it over get_asset, screen_candidates, or search_marketplace. The only explicit guidance is interpretive ('do not interpret null as zero'), not selection guidance.

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