market_get_cex_fund_flows

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description only needs to add contextual behavior. It adds the data source (DefiLlama CEX tracker) and indicates return content (inflow/outflow amounts), but it does not disclose details like default limit behavior, ordering, or time range. This is adequate but not rich.

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 two sentences, front-loads the action and resource, and avoids filler. Every clause contributes useful context about the data source and output.

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, rich annotations, and no output schema, the description sufficiently covers tool purpose and return content. It could mention time range, units, or sorting, but for a simple retrieval tool it is complete enough to guide correct usage.

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 'limit' is already fully described in the schema as 'Maximum number of results to return', so schema coverage is 100%. The description adds no additional meaning about the parameter, matching the baseline where the schema carries the explanatory burden.

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 'Fetch' and clearly identifies the resource: net fund flow data for centralized exchanges from DefiLlama's CEX tracker. It also states the output includes inflow and outflow amounts per exchange, which distinguishes it from sibling market tools like market_get_exchange_rankings or market_get_dex_volume.

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 a clear use case: 'useful for monitoring capital movements on CEXes.' It does not explicitly name alternatives or exclusion criteria, but the CEX-specific scope makes the intended context reasonably clear without needing extensive comparison to siblings.

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