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

With no annotations provided, the description must carry the behavioral disclosure burden. It only adds 'with lag in seconds' as a behavioral detail; it does not disclose whether this is read-only, what data is returned, pagination behavior, or any limitations.

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 compact sentence with no filler. It front-loads the core concept and includes the notable 'lag in seconds' detail, though the sentence is structurally incomplete as a definition.

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?

There is no output schema, so the description should clarify what the tool returns and how to interpret the results. It defines the concept but does not explain the output shape, parameter effects, or practical usage context, leaving an agent to guess at the response format.

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 does not mention the limit or window parameters at all. The schema names and enums are somewhat self-explanatory, but the description adds no semantic value about how these parameters affect the returned copy-flow data.

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 identifies a specific resource and concept: copy-flow data showing a FOMO lead buy and the wallets that followed into the same token, with lag in seconds. This is reasonably distinct from the many sibling talon_* tools, though it is phrased as a noun phrase rather than a clear verb+resource statement.

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 gives no guidance on when to use this tool versus the numerous siblings such as talon_calls, talon_traders, or talon_cohort. There are no explicit contexts, exclusions, or alternative routing signals.

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