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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention whether the tool is read-only, what data it observes, how it presents results, or any side effects. 'Monitoring' implies passivity but is not explicit.

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 concise, single phrase with no redundant content. 'Bridge flow monitoring for Sui' front-loads the core purpose without wasting words.

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?

The description is too sparse for a tool with no output schema. It does not clarify what bridge flows are, what specific metrics are provided, or how the output is structured. An agent would be uncertain what data to expect from this 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?

The input schema has zero parameters and additionalProperties is false, so there is nothing to explain. Following the rubric, 0 parameters earns a baseline score of 4.

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 'Bridge flow monitoring for Sui' – a specific resource (bridge flows) and an actionable purpose (monitoring). It is distinct from sibling tools like sui_dex_volume or sui_defi_yields, though 'flows' remains somewhat ambiguous (e.g., transaction volume vs liquidity movements).

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?

No guidance is provided on when to use this tool, what it should be used for, or when to prefer alternatives. There is no mention of use cases, prerequisites, or exclusions, leaving the agent without decision support.

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