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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds genuinely new behavioral context by explaining how to interpret results (inflow = bullish, outflow = bearish), which annotations cannot convey. It omits freshness/lag or rate-limit behavior, so it falls short of a 5.

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?

Four short sentences, front-loaded with the core purpose and followed by interpretation, usage and alternatives. The bullish/bearish parenthetical is useful rather than wasteful, but the routing sentence is slightly dense and could be trimmed.

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?

With an output schema present, the description need not explain return structure; combined with rich annotations and a fully documented single parameter, everything an agent needs to call and interpret this tool correctly is present.

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%: the sole 'chain' parameter has an enum, a default, and a description enumerating supported chains. The description only implies the 'one chain' scope and adds no syntax or format detail beyond the schema, so the baseline of 3 is 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?

States a specific verb (Analyze) and resource (cross-chain bridge capital flow direction) with explicit interpretation of the output as bullish inflow vs bearish outflow. It names an alternative tool (chain.bridge.monitor) so an agent can distinguish it from adjacent bridge functionality without opening schemas.

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 states the use case (directional net capital flow across bridges on one chain) and routes two alternatives: chain.bridge.monitor for large-transfer detection and chain.compare for chain selection. Conditions for choosing this tool over siblings are unambiguous.

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