util_streaks

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

No annotations are provided, so the description must disclose behavioral traits. It states the tool returns segment length and amplitude percentage but does not explain edge cases (e.g., equal prices, single-segment sequences) or whether it modifies data. As a read-only analysis, it is minimally adequate but lacks comprehensive behavioral context.

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 sentence that conveys the tool's purpose and output efficiently. No extraneous information; every phrase earns its place. Front-loaded with the core action.

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?

No output schema exists, so the description should fully explain return values. It mentions 'length and amplitude percentage' but does not specify data types, structure, or how segments are defined (e.g., monotonic changes). For a simple utility, it is adequate but leaves some ambiguity.

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 schema has 100% coverage with descriptions for both parameters. The description adds '价格序列' for prices and '统计方向：up（上涨段）/ down（下跌段）' for keepSide, which slightly expands on the schema but does not provide meaningful new semantics. Baseline 3 due to high schema coverage.

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 clearly states the tool counts continuous up/down segments of a price sequence and returns length and amplitude percentage. It uses a specific verb (统计/count) and resource (价格序列/price sequence), distinguishing it from sibling indicator tools that compute technical analysis metrics.

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 lacks guidance on when to use this tool versus alternatives. It does not provide context like 'use this to analyze consecutive price movements' or mention exclusions or prerequisites. No explicit differentiation from sibling utility tools like util_extract_klines or util_grid.

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