polynodes_send_raw_osc

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds only 'Returns: JSON confirmation' and does not disclose that arbitrary addresses can mutate synth state in unrecoverable or unclear ways, nor any validation/error behavior for invalid OSC paths.

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?

Front-loads the purpose in one sentence and keeps supporting detail to short Args/Returns blocks; nothing is redundant or padding. The scaffolded 'Args:'/'Returns:' boilerplate is slightly mechanical but not wasteful.

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?

Annotations cover the safety and world-interaction profile and an output schema exists, so return values need not be explained. With two fully documented required parameters and a stated universal address scope, an agent has enough to invoke it correctly.

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% and both parameters already carry descriptions and an example address, so the schema does the heavy lifting. The description's Args block largely restates the schema fields with no added format, range, or addressing conventions.

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?

States a specific verb and resource ('Send a raw OSC message to PolyNodes') and signals the escape-hatch nature of the tool with 'any OSC address', which distinguishes it from the many named setters like polynodes_set_gain. It does not explicitly contrast itself with those siblings, so it stops short of a 5.

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?

'Use this for any OSC address' implies the tool is the general-purpose path when a dedicated setter does not exist, but it never states when to prefer the specialized siblings or when to call polynodes_list_osc_addresses to discover valid addresses. Usage is implied rather than spelled out.

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