24h whale digest

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

No annotations are provided, but the description discloses the key behavioral trait: 'PAID (~$0.02).' It also conveys a read-only digest operation through '24h digest' and lists the data contents. It does not mention output format or failure behavior, but for a zero-parameter data retrieval tool this is a reasonable level of disclosure.

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 short segments with no wasted words. It front-loads the critical cost warning ('PAID') and then gives a tight, informative list of digest contents.

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 the zero-parameter schema, no annotations, and no output schema, the description covers the essential context: cost, time window, and content categories. It is slightly light on exact definitions like what 'totals' means or how results are structured, but it is complete enough for such a simple 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?

There are zero parameters, so the baseline is 4. The description adds no parameter information, but none is needed since the input schema is empty and schema coverage is effectively complete.

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 says '24h digest: top markets by whale volume, net flow, largest single bets, totals' with a verb-plus-resource structure that clearly defines what the tool returns. It is easily distinguished from siblings like predge_whales_latest and predge_signals_daily_category by the '24h digest' framing.

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 '24h digest' phrase establishes a clear context for when to use this tool: getting a daily summary of whale activity. It does not explicitly name alternatives or exclusions, but the strong temporal scope and content list provide sufficient guidance for typical selection.

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