monitor_fan_token_transfers

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

With no annotations, the description carries the full behavioral burden. It only hints at 'real-time' behavior but omits critical details such as whether it starts a persistent subscription, blocks execution, returns a stream or handles, requires WebSocket connectivity, or how it is stopped (e.g., via stop_all_monitoring).

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, front-loaded sentence with zero wasted words. It communicates the core action immediately and efficiently.

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 real-time monitoring tool with no annotations and no output schema, the description is insufficient. It does not explain what the tool returns, whether it runs indefinitely, how to stop it, or how it interacts with the existing stop_all_monitoring sibling.

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 100%, so the schema already fully documents both tokenAddress and tokenSymbol. The description adds no extra meaning beyond what the input schema provides, making the baseline score of 3 appropriate.

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 specific verb ('monitor') and a clear resource ('real-time transfers of a specific fan token'). It does not, however, differentiate this tool from other monitoring siblings such as start_log_monitoring or detect_whale_trades, leaving the agent to infer the distinction.

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?

There is no explicit guidance on when to use this tool versus alternatives like start_block_monitoring, start_log_monitoring, or detect_whale_trades. The description provides only an implied use case, not when-not-to-use or prerequisite conditions.

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