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 of behavioral disclosure. It reveals that the export happens 'via expression' and implies a link from CHOP data to a parameter, but it doesn't describe what happens to existing parameter expressions, whether the export is dynamic or static, any required permissions, or side effects on the CHOP network. This is a minimal disclosure of behavior.

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 a single, focused sentence that front-loads the core action and resource. There is no redundant language or filler. While it lacks detail, that deficiency is captured in other dimensions; for what it does include, the structure is clear and concise.

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?

This is a four-parameter tool with no annotations, no output schema, and no additional context. The description only states the high-level purpose. It fails to explain the meaning of the parameters, the required setup, how the expression is generated, or what the agent should expect as a result. Given the tool's complexity and the lack of structured metadata, the description is grossly insufficient for safe and correct invocation.

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%, and the description provides no explanation of the four parameters (chop_path, channel_name, target_path, parm_name). It doesn't even mention parameter names or how they relate to the export process. An agent would be completely dependent on the bare schema titles without any added 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 'Export' and clearly identifies the resource ('CHOP channel') and the destination ('a parameter via expression'). It stands out from sibling tools like set_expression and get_chop_data because it specifically targets CHOP-to-parameter export. However, it doesn't explicitly contrast with set_expression, which also deals with parameter expressions, so it doesn't fully distinguish itself.

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 guidance is provided about when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., an existing CHOP network or parameter) or scenarios where another tool like set_expression or list_chop_channels would be more appropriate. The description simply states the action without contextual usage advice.

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