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

Annotations already establish this as a read-only, idempotent operation. The description adds valuable behavioral context by warning that a single large transfer may be an exchange rebalancing its own wallets, not a genuine distribution or accumulation signal. This goes beyond the annotations and helps the agent interpret results correctly.

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 well structured and front-loaded with the core definition, followed by concise interpretive context and a caution. Every sentence adds value, and there is no redundancy or filler.

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 conceptual semantics are well explained, and the warning about rebalancing is useful. Still, with no output schema and no mention of the symbol parameter or expected return shape, the description is not fully complete for an agent to invoke the tool with confidence.

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 description coverage is 0%, and the description never mentions the 'symbol' parameter, its format, or behavior when omitted or null. Saying 'of an asset' only implicitly references the parameter, which is insufficient to compensate for the lack of schema documentation.

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 states a clear verb and resource: reporting the net movement of an asset into and out of exchange wallets. It adds meaningful definitions of inflows and outflows, but it does not distinguish this tool from the closely named sibling get_exchange_netflow, so it falls short of full differentiation.

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 useful context about when to trust the conventional distribution/accumulation reading and explicitly advises checking get_entity_flows before attributing intent. However, it gives no guidance on when to use this tool versus get_exchange_netflow, which appears to be a near-duplicate based on name alone.

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