set_rssi_offset

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

Description provides range and default for the parameter, but no annotations exist to cover safety or destructiveness. It fails to disclose whether the change is persistent, requires a save/reboot, or if it has side effects on other settings. As a write operation, more behavioral context is needed.

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: a single sentence with all essential information (purpose, type, range, default). No wasted words; highly efficient for a simple parameter setter.

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 straightforward setter with one parameter and no output schema, the description covers the core purpose, constraints, and default. It lacks mention of persistence or effect timing, but given the tool's simplicity, it is largely complete.

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 100% with the same range and description as the tool description. The description adds only the default value (0) beyond the schema, offering minimal additional semantic value. Baseline score of 3 is appropriate.

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?

Description clearly states the tool sets the RSSI offset with specific verb 'Set' and resource 'rssi_offset'. Specifies the action as 'Offsets the RSSI reading', distinguishing it from siblings like set_rssi_channel or set_rssi_scale which have different purposes.

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 or any prerequisites. The description only states what the tool does without context such as typical scenarios or conditions where adjusting RSSI offset is appropriate.

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