get_northbound_realtime

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

Annotations already declare readOnlyHint=true, so the safety profile is known. The description adds value by stating the tool returns both intraday inflow curves and a Stock Connect summary in one call, which is useful behavioral context beyond the annotations.

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?

A single sentence concisely packs the tool's purpose, output, and use case with no redundancy or filler. Perfectly sized for one simple parameter.

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 tool's simplicity, no output schema, and one parameter, the description adequately explains what the tool returns and why it is used. It could mention update frequency or more detail about the data, but it is not necessary for basic invocation.

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 coverage is 100% with the 'direction' parameter fully described (north/south, default north). The description merely mentions '北向/南向' without adding new syntax or details, 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?

Description clearly states the tool fetches real-time northbound/southbound capital data, returning intraday inflow curves and Stock Connect summary. This distinguishes it from siblings like get_northbound_history and get_northbound_holding_rank.

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 phrase '用于判断当日外资动向' implies usage context (judging the day's foreign capital trends), but there is no explicit comparison to alternatives or exclusion criteria. Usage guidance is implied rather than stated.

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