fusion_cam_post_process

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

With no annotations, the description carries the full burden. It discloses that the tool is experimental and writes to an output folder, but it does not state whether it modifies the document, whether it is destructive, whether it requires prior generation, or what happens if the output folder is not empty. The warning to inspect results is useful but vague.

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 short and front-loaded with the experimental warning, but the second sentence is generic and adds little. It earns a middle score because it is compact, though not optimally informative.

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 3-required-parameter tool with no annotations and no output schema, the description is incomplete. It does not explain prerequisites, side effects, expected outputs, or how to interpret the result. The experimental warning is the only contextual signal.

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 does not explain any of the three required parameters (document_id, operation_id, program_id). The agent must guess what 'operation_id' and 'program_id' refer to and how they relate to the post-processing step.

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 says 'post-process the explicitly configured NC program to its empty output folder' which names a verb and resource, but the opening 'Experimental, not yet live-validated' and the vague 'Inspect results and machine/post suitability before machining' muddy what the tool actually does. It does not clearly distinguish from siblings like fusion_cam_generate or fusion_cam_create_nc_program.

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 a workflow step ('before machining') but gives no explicit when-to-use or when-not-to-use guidance. It does not name alternatives or explain how this differs from fusion_cam_generate or fusion_cam_job.

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