get_force_battery_cell_count

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

No annotations provided, so description bears full burden. It explains the tool overrides auto-detection and gives value semantics, but lacks broader behavioral context (persistence, permissions, side effects on other settings). Adequate for a simple getter.

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?

Extremely concise: one sentence plus range/default notation. Every word adds value. No redundancy. Front-loaded with action and purpose.

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?

Adequate for a simple parameter getter: explains value meaning and range. However, does not explicitly state that it returns the current setting value, nor mention any related configuration (e.g., set_force_battery_cell_count). Output schema absent, so description could clarify return type.

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?

Input schema has zero parameters, baseline 4. Description adds meaning by explaining that the returned value represents forced cell count override (0 = auto-detect), which is valuable beyond the empty schema.

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 retrieves the forced battery cell count override, explains special value 0 meaning auto-detect, and specifies range [0-24] with default. It distinguishes from the sibling setter by naming convention, but does not explicitly compare to similar get tools like get_vbat_max_cell_voltage.

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?

Minimal guidance: explains 0 means auto-detect, implying use this to read override. No explicit when-to-use or when-not-to-use compared to alternatives (e.g., get_vbat_max_cell_voltage or get_battery). Sibling setter exists but not referenced.

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