compress_smash

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 states the effect ('aggressive parallel-style compressor') but does not explain whether the operation is destructive, how it modifies the track, or what the result will be. Furthermore, the assertion 'No params — preset values' directly contradicts the input schema which includes a required track_id, undermining trust in the description.

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, but the misleading statement about parameters wastes the limited space. It front-loads the purpose but then introduces inaccuracy, making the overall structure counterproductive. A well-structured description would clarify the parameter requirement.

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 tool with one required parameter and no output schema, the description should at least explain the track_id and the effect of the operation. It does neither, and the misleading 'no params' claim leaves the agent without necessary context to invoke the tool safely and correctly.

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 by explaining the track_id parameter. It not only fails to explain it but actively claims there are no parameters, making the parameter completely opaque. This is a serious failure to add meaning beyond the schema.

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 identifies the tool as an aggressive parallel-style compressor for drum-bus / NY-style smash, which is a specific use case. However, it does not differentiate from the sibling tool compress_glue, which likely serves a similar purpose, so it lacks sibling differentiation.

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 for drum-bus/NY-style scenarios but provides no explicit guidance on when to choose this over compress_glue or other compressors. The claim 'No params — preset values' is misleading because the schema requires a track_id, leaving the agent uncertain about how to invoke the tool correctly.

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