fahali_get_whale_activity

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

With no annotations, the description fully discloses the behavioral trait: the tool returns ABSTAIN status and does not fabricate data. It explains the abstention reason and return structure clearly.

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, information-packed sentence. While it contains all necessary details, it could be slightly more concise. However, it is well-structured and front-loads the abstain policy.

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 zero parameters, no output schema, and no annotations, the description fully explains the tool's behavior, return values, and abstention rationale. It is complete for a tool that does nothing.

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?

No parameters exist, so baseline is 4. The description adds value by explaining the abstain behavior and return structure, which is not apparent from the empty schema.

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's purpose: to abstain from whale tracking due to lack of data, returning a specific status and empty activities. It also distinguishes itself from sibling tools by naming alternatives like fahali_get_market_verdict.

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?

Explicitly tells when the tool abstains and provides direct alternatives (fahali_get_market_verdict and fahali_get_realtime_alerts) for actual detections, offering clear usage guidance.

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