get_drum_chains

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

No annotations are provided, so the description carries the burden. It discloses the return contents but does not state whether the operation is read-only (though 'Get' implies it), what happens if the device is not a Drum Rack, or whether any side effects occur. The zero-based indexing info is useful but is more parameter 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: a purpose statement, a return summary, and a parameter list. No wasted words; structure is clear.

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 is simple with an output schema, and the description summarizes what is returned. It mentions the Drum Rack requirement and the key fields, making it sufficient for most uses. However, it could be slightly more complete regarding error cases or the structure of the output, but the output schema covers that.

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 description provides concise explanations for both parameters, specifying zero-based indexing and clarifying that device_index refers to a drum rack device. This fully compensates for the 0% 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 the tool retrieves drum-chain-specific properties from a Drum Rack, listing the specific returned data (name, mixer values, note/choke settings). This distinguishes it from sibling tools like get_drum_pads and set_drum_chain_property.

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 implies usage when drum chain properties are needed but does not explicitly mention alternatives or when not to use it. It lacks explicit comparison to get_rack_chains or set_drum_chain_property, though the purpose makes it inferable.

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