Read Raw Register

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

Annotations already provide readOnlyHint=true and destructiveHint=false. Description adds that it is advanced and requires prior lookup from other tools, plus the Modbus TCP only limitation. No contradiction.

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?

Two concise sentences. First sentence covers core function and protocol limitation. Second adds essential usage guidance. No wasted words.

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 7 parameters, 3 required, full schema descriptions, and an output schema present (though not shown), the description provides necessary context and preconditions. Guidance on using other tools first completes the picture for correct usage.

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?

All 7 parameters are described in the input schema with 100% coverage. The description adds no additional parameter meaning beyond stating 'explicit data type and scale factor', which are already in schema. Baseline 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?

Clearly states it reads raw Modbus register(s), specifies Modbus TCP only, and distinguishes itself as an advanced tool for specific register addresses. References sibling tools (victron_search_docs, victron_list_registers) for pre-work.

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?

Explicitly instructs to use victron_search_docs or victron_list_registers first to find correct address, data type, and scale factor. Also notes it's only for Modbus TCP, not MQTT, providing clear when-to-use and when-not-to-use guidance.

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