fusion_cam_create_nc_program

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

With no annotations provided, the description carries the full burden and it does disclose two real behavioral facts: the tool is 'Experimental, not yet live-validated' and produces an empty output folder without post-processing. These exceed what the schema conveys. However, it does not disclose authorization needs, side effects, or what the return looks like, leaving gaps for a mutation-style tool with zero annotation coverage.

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?

It is compact — a single sentence with essentially no wasted words, and the safety-relevant 'Experimental' warning is front-loaded. But it is under-specified rather than merely concise; a structured split between purpose and limitations (e.g., a separate note on the empty output / pending post-process) would serve an agent better without adding bulk.

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?

Given 3 required top-level parameters plus a nested spec with 5 fields, no descriptions in the schema, and no output schema, the description is materially incomplete. It does not explain that NC program creation follows an existing CAM workflow, nor what document_id/operation_id refer to, nor what the agent should expect in response. For an experimental tool this ambiguity is risky.

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 undocumented parameters. It fails to do so — only a passing reference to 'chosen post' and 'empty output folder' hints at post_url and output_folder. The critical parameters operation_ids, document_id, operation_id, and the filename pattern (^[A-Za-z0-9_-]+$) are left entirely unexplained.

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 a specific verb ('prepare') and resource (NC program) with a chosen post and empty output folder. It distinguishes from the sibling fusion_cam_post_process by explicitly noting 'does not post-process yet'. The verb 'prepare' is slightly vague versus 'create', but the scope is adequately conveyed.

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 on when to use this tool versus alternatives. The phrase 'does not post-process yet' implicitly hints that post-processing is a separate later step, but the description never names fusion_cam_post_process or any other sibling, nor states when this tool is preferred over fusion_cam_create_setup or fusion_cam_create_operation.

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