xr18_get

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Get', implying a read operation, but does not explicitly state it has no side effects, nor does it describe error handling, return format, or connection requirements. This is a significant gap for a hardware-interfacing tool.

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 a single short sentence with no redundant words. It front-loads the action and the key constraint (exact native OSC value) efficiently, making it easy to parse.

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 the tool has one parameter, no output schema, and minimal annotations, the description is sparse. It does not explain what a 'mixer parameter' encompasses, what the return value looks like, or how to construct a valid OSC path. While it may suffice for an expert, an agent would need more context to invoke it correctly across the sibling tool ecosystem.

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 schema has a single 'path' parameter with zero description coverage. The description adds that the path should be an 'exact, native OSC value', which clarifies it is an OSC address, but does not give format examples or accepted patterns. This partially compensates for the 0% schema coverage but is not comprehensive.

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 verb 'Get' and the resource 'mixer parameter', and specifies the use of 'exact, native OSC value', which distinguishes it from set/trigger operations. However, it does not differentiate from sibling getters like xr18_get_send_db or xr18_get_fader_db, which may be more specific wrappers.

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 the many sibling getter tools. It does not mention alternatives, conditions, or exclusions, leaving the agent to infer that this is the generic low-level getter without explicit routing information.

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