util_streaks

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

With no annotations, the description bears full responsibility for behavioral disclosure. It omits crucial details like the return format (e.g., an integer count) or how the counting is performed (e.g., consecutive from start or end).

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 extremely short (4 characters), which is concise but lacks sufficient detail. It does not front-load key information or provide a complete sentence that adds value.

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 lacks completeness: no output schema exists, and the description does not explain what the tool returns (e.g., count of consecutive days). For a simple tool with two params, more context is needed.

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%; both parameters have Chinese descriptions meaning 'price array' and 'direction'. The tool description adds no additional meaning beyond the schema, so it scores the baseline of 3.

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 'calculate consecutive rises and falls' clearly states the tool computes streaks of price movements. It distinguishes from sibling utilities like util_average or util_max, which perform different operations.

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 on when to use this tool versus alternatives. The description does not specify appropriate contexts, such as financial time series analysis, or indicate that it should be used when streak counting is needed.

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