export_chop_to_parm

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

With no annotations, the description carries the full burden. It hints that the target parameter receives a chop() expression but doesn't disclose that existing values/expressions are overwritten, that the CHOP path/channel must exist, or that the parameter is mutated. Critically important behavior is left out.

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: one intro line followed by a structured argument list. No redundant filler. It earns its place but omits additional needed context.

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 mutation tool with four string parameters and no annotations, the description is too shallow. It doesn't cover prerequisites, side effects, or failure modes, and with no output schema, the agent has to guess the result shape and error conditions.

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. The argument list adds minimal meaning beyond the parameter names (e.g., 'channel_name: Channel to export' restates the name). Only 'target_parm_name' gets a slightly more informative note. This is not enough to truly explain inputs.

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?

States the operation clearly: exports a CHOP channel to a parameter via a chop() expression. The verb, resource, and mechanism are specific enough to identify the tool, though it doesn't explicitly contrast it with sibling tools.

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?

No usage guidance is provided. The description doesn't say when to use this tool over alternatives like set_parameter, set_expression, or link_parameters, and it gives no conditions, exclusions, or prerequisite context.

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