fenwick_range

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

No annotations are provided, so the description carries the full disclosure burden. It notes the implementation uses two BITs but says nothing about output shape (does it return the final array, a list of query results, or nothing?), complexity, or constraints on the operation list — the details an agent actually needs for a computation tool.

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 front-loaded sentence with no filler; every clause carries information. It is arguably too terse for the amount of undocumented behavior, but there is no wasted text.

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 no annotations and no output schema, the description is the only source of behavioral detail, and it omits what the tool returns and how operations are encoded. For a two-parameter algorithmic utility whose whole contract lives in the operation format, that leaves a meaningful gap.

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 nominally 100%, so the baseline is 3, and the description does add the context that operations span range-update as well as range-query semantics. However, the schema's `operations` entry only says '{type, left, right, value?} operations' without enumerating the accepted `type` tokens, and the description does not supply them either.

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 names a concrete data structure and states its capability precisely: a Fenwick tree supporting both range update and range query via two BITs. That is enough to separate it in spirit from fenwick_tree (point update + range query) and fenwick_2d, but it never names those siblings, so the differentiation is inferred rather than explicit.

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?

There is no when-to-use guidance and no mention of fenwick_tree or fenwick_2d as alternatives, even though three near-identical Fenwick tools exist in the sibling list. The agent must guess which variant applies from the capability phrase alone.

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