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

No annotations are provided, so the description carries the full burden. It explicitly describes the return values (flow_state with five distinct states) and the input format (Robinhood-chain 0x or Solana base58). It implies a read-only query by framing the tool as a signal detector, but it doesn't explicitly state there are no side effects. Given the context, this is adequate.

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 moderately verbose but front-loaded with the core purpose and includes a list of possible return states. It is structured logically, with the usage tip at the end. It earns a high score for efficiency, though it could be tightened.

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 single-parameter, read-only signal tool with no output schema, the description is fairly complete. It explains the return states, the input format, and when to use it. It lacks explicit error handling or edge-case details, but these are minor given the simplicity of the tool.

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 coverage is 100% for the single 'token' parameter, and the description's mention of formats (Robinhood-chain 0x or Solana base58) exactly matches the schema description, adding no new information. The description does not elaborate beyond what the schema already specifies, so it stays at the baseline for full 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 detects a temporal money-flow direction flip for a token, enumerates the specific flow_state values, and explicitly contrasts it with a static snapshot. This distinguishes it from siblings like check_mint or score_mint, which serve different purposes.

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?

It provides a clear usage context: 'Call before an entry to avoid buying a top a static footprint would miss.' This implies when to use it and suggests it complements (rather than replaces) static analysis, but it doesn't name specific alternative tools or state when not to use it.

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