device_property

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

With no annotations, the description carries full behavioral burden. It usefully discloses the read-vs-write trigger (omitting value) and gives a value-semantics example, but says nothing about permissions, side effects of setting, chaining behavior, or error cases for a 7-parameter mutation 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?

A single compact sentence with the read/set distinction front-loaded and the illustrative example trailing. Efficient, though the parenthetical grouping makes the mode semantics slightly harder to parse than it needs to 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?

For a 7-parameter mutation tool with no annotations and no output schema, the description is far too thin: it does not cover most parameters, chain/chain-device nesting, or the effect of setting a property. An agent would be guessing on the majority of the call surface.

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 0%, so the description must compensate. It only clarifies the value parameter (omit for read) and one enum example under name ('voices'); it leaves kind, track_index, device_index, chain, and chain_device entirely unexplained.

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 states a specific verb pair ("Read ... or set") and a clearly bounded resource ("a device property that is not an automatable parameter"), which implicitly separates it from the sibling parameter tools. However, it never names get_device_parameters/set_device_parameters directly, so the agent must infer the boundary itself.

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?

It gives a usable mode switch ("value omitted" = read, provide value = set) and a concrete scenario (Simpler 'voices', 1 = mono for 808 glide). It lacks explicit exclusions or a named alternative for automatable parameters, so the routing is clear-context rather than fully specified.

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