Set conserve activation threshold

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

With no annotations, the description carries the burden of transparency. It explains the behavioral effect of the threshold value, such as 0 meaning conserve whenever a reading succeeds and requests remain, and 80 meaning conserve only near the limit. This provides meaningful insight into the tool's behavior, though it does not cover all potential side effects (e.g., persistence or authorization).

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 three concise sentences, front-loaded with the main purpose, and contains no redundant information or fluff.

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?

For a simple setter with one parameter, no annotations, and no output schema, the description is sufficiently complete. It explains the parameter semantics and gives behavioral examples, covering all essential aspects needed for an agent to use the tool correctly.

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 description fully explains the activationThresholdPct parameter by stating it is a usage percentage from 0 to 100 and providing examples. Since the schema has no description for the parameter, this is essential and effectively compensates for the 0% schema description 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 states specifically that it sets the minimum usage percentage at which conserve mode activates. This is a clear verb+resource pair, and it distinguishes from sibling tools like set_verbose or set_followup.

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 provides clear context by explaining the default (0) and giving an example (80), but it does not explicitly discuss when to use this tool versus alternatives. However, the given examples imply appropriate usage scenarios.

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