get_vbat_cutoff_percent

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

No annotations are provided, so the description must fully convey behavioral traits. It states that the tool 'gets' a setting, implying a read-only operation with no side effects. However, it does not explicitly confirm that it only reads a configuration value and does not modify any state. While a simple getter has limited behavioral complexity, the description could be more explicit.

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 concise: one sentence explaining the purpose, plus a bracket notation for the data type, range, and default. Every element adds value, and there is no wasted space. It is front-loaded with the essential information.

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?

Given that the tool has no parameters and no output schema, the description adequately explains what the return value represents (percentage, meaning, range, default). It is complete for a simple getter, though it could potentially benefit from mentioning how this value interacts with other settings (e.g., it is used in conjunction with vbat_sag_compensation).

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 tool has no parameters (input schema has no properties), so schema coverage is complete by default. The description adds no parameter information because none is needed. This is appropriate for a parameterless tool.

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 that the tool retrieves the vbat_cutoff_percent setting, specifying its meaning as the percentage of vbat_sag_compensation to apply at critically low voltage. It also includes the data type, range (0-100), and default value (100). This is specific and distinguishes it from other getter tools in the sibling list.

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 no guidance on when to use this tool versus alternatives. It does not specify prerequisites, context, or differentiate it from other vbat-related getters such as get_vbat_sag_compensation or get_vbat_warning_cell_voltage. The agent is left without explicit usage direction.

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