tb_send_rpc

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action without mentioning whether the command is fire-and-forget, whether a response is returned, or what side effects occur. This is insufficient for an RPC operation.

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 only seven words, which is concise but at the cost of crucial details. This is under-specification rather than effective conciseness; it omits prerequisites, return behavior, and usage context, making it less practical than it should be.

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?

The tool has 4 parameters (including a nested object) and no output schema, yet the description does not explain the response format, error handling, or device availability requirements. This is a significant gap for a command-sending tool, making the description inadequate for safe and correct invocation.

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 description coverage is 100%, so the baseline is 3. The description itself adds no parameter information, but the schema provides some descriptions. However, the distinction between device_id and tb_device_id is ambiguous, and the tool description does not clarify the semantics beyond what the schema states.

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 primary action ('Send RPC command') and the target ('ThingsBoard device'), which identifies the tool's core function. However, it does not elaborate on what RPC entails or differentiate it from sibling tools like iot_execute_command, so it slightly misses full distinction.

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 is provided on when to use this tool versus alternatives such as tb_device_telemetry or iot_execute_command. The description lacks prerequisites, context, or examples that would help an agent decide to invoke this tool.

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