x2d_native_control

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

With no annotations, the description carries full burden. It usefully discloses that operations run 'through the installed plug-in' and that entire command classes are rejected, but it says nothing about permissions/authentication, reversibility of the AMS metadata updates, or return behavior. Real added value, but incomplete for a read+write tool.

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?

Two tight sentences, front-loading purpose then constraints, with zero padding. Only minor deduction because 'X2D' is an unglossed term an outside agent may not recognize.

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?

No output schema and no annotations mean the description must cover more ground. It establishes domain and rejected command classes but leaves the mutation semantics, expected responses, and the relationship to sibling network tools unaddressed, so it is adequate but not complete.

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 100%, and message_json already enumerates the supported commands (ams_filament_setting, extrusion_cali_sel, etc.). The description adds no syntax, format, or sequencing detail beyond that, so the baseline of 3 applies.

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 specific verbs (read/update) and resources (calibration results, X2D AMS metadata/calibration selection) and names the mechanism (installed plug-in), so the agent knows this is a native-control passthrough. It does not explicitly differentiate from lookalike siblings such as bambu_network_call, keeping it at 4 rather than 5.

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 gives a negative scope ('raw motion, heating, task control, and safety-setting changes are rejected'), which tells the agent what this tool will not do. However, it names no positive when-to-use conditions and no alternative tool for the rejected operations, leaving usage largely implied.

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