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

With no annotations provided, the description carries the full burden of explaining behavior. It implies a read-only monitoring operation but does not explicitly state that it avoids mutations, nor does it disclose any data freshness, return format, or system effects. This lack of detail leaves significant ambiguity about the tool's runtime behavior.

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 concise sentence with no redundant words. It is front-loaded with the core purpose and is appropriately sized for a tool with no parameters and a straightforward monitoring function. Every word contributes to conveying what the tool does.

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 absence of annotations, output schema, and parameters, the description is extremely sparse. It does not explain what data is returned, the time range covered, or how the user might interpret 'bridge flow'. In the context of nine sibling tools, more detail is needed to enable correct selection without additional assumptions.

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?

The input schema is empty with zero parameters, so there is no parameter semantics to clarify. The description adds no parameter information because none exist. As per the baseline for zero-parameter tools, this is sufficient.

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 'Bridge flow monitoring for TON' clearly identifies the tool's resource (bridge flows) and action (monitoring), and it distinguishes itself from sibling tools such as ton_dex_volume and ton_network_stats, which address different domain areas. However, it lacks a specific verb like 'get' or 'list' and does not elaborate on what aspect of bridge flows is captured, so it is clear but not fully specific.

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 provides no guidance on when to use this tool versus alternatives. It does not mention what scenarios this is appropriate for, nor does it name any sibling tools for comparison. It only states what it does, leaving the agent to infer usage context.

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