fusion_cam_post_process

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

While annotations indicate a write operation, the description does not disclose side effects (e.g., file overwriting), required permissions, or error conditions. It mentions a default output folder but does not clarify behavior when the folder exists or when outputs already exist.

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 sentences, no redundancy. However, the second sentence ('post_processor is a generic post name') is somewhat ambiguous and could be integrated more clearly.

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 5 parameters, no output schema, and minimal description, the tool lacks crucial information: how the G-code file is named, error scenarios, locale/units handling, and what happens when operation is null. The description is insufficient for effective tool selection and 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?

With 0% schema description coverage, the description only loosely explains setup, operation, and post_processor. It does not define units, output_folder (despite mentioning a default path that conflicts with schema's null default), or provide parameter format/constraints.

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 clearly states the tool's action ('Post-process') and resource ('a setup (or one operation)'), with a specific output (G-code file) and a default location. This distinguishes it from sibling tools like fusion_cam_create_operation or fusion_cam_generate.

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 provides no explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or when not to use it. The mention of post-processing setup or operation is implicit but does not contrast with similar tools like fusion_cam_generate.

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