get_master_device_parameters

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It only states 'Get parameters' (implicitly read-only) but does not mention return format, side effects, error conditions, or any constraints. The extra Master track context adds little about behavior beyond the obvious getter semantics.

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 concise and front-loaded with the primary action. The parameter listing is clear and structured. The sentence about the Live API is slightly redundant but adds useful context for why the dedicated command exists, so it earns its place.

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 simple one-parameter getter, the description covers the tool's purpose, target track, and parameter meaning. It omits return value details, but given the tool's simplicity and the absence of an output schema, the provided information is largely sufficient. Minor gap: no description of the returned parameter structure.

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 provides only the bare field name and type, so the description's 'Parameters' section adds crucial meaning by defining device_index as 'The index of the device on the Master track'. While it doesn't add range or formatting details, it fully explains the semantic role of the parameter, compensating for zero schema description coverage.

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 'Get parameters of a device on the Master track' with a concrete example (mastering compressor), making the tool's function immediately obvious. It distinguishes itself from sibling tools like get_device_parameters by focusing exclusively on the Master track.

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 explains the dedicated nature of the command ('the Live API reaches them fine; they just need this dedicated command'), implying it should be used for Master track devices rather than the generic device retrieval tool. However, it does not explicitly list when not to use it or name alternatives, but the context is clear.

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