get_track_fx_chunk

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

Annotations already declare readOnlyHint=true, and the description adds useful behavioral context by explaining that the tool returns the full serialized plugin state and specifying the return shape: 'Object with "chunk" containing the FX state data string.' This goes beyond the minimal annotation without contradicting it.

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 short, front-loaded with the core action, and includes a concrete use case and return shape. Every sentence adds value, though the phrase 'includes preset/state data' is somewhat redundant with 'full serialized state.'

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 description explains what the tool returns and gives a practical example, but it does not clarify how the two parameters map to the track/FX context, differentiate track FX from take FX (relevant given sibling tools like take_fx_get_name), or describe potential edge cases. It is adequate for a simple read tool but leaves some gaps.

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 for explaining track_index and fx_index. It does not mention either parameter or describe how they identify the plugin, leaving the agent to infer from names alone. The parameter names are somewhat self-explanatory, but the description adds no semantic guidance.

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 uses a specific verb and resource: 'Get the raw state chunk from an FX plugin.' It distinguishes itself from related FX tools by emphasizing 'raw state chunk' and 'full serialized state,' which clearly separates it from preset-name or parameter-level getters like get_fx_preset or track_fx_get_name.

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 a clear use case: 'Useful for reading VSTi state data like Toontrack EZkeys chord progressions.' This gives context for when to use the tool, though it does not explicitly mention alternatives or when not to use it.

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