ms_gui_forcite_optimize_current

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

No annotations are provided, so the description carries full burden. It mentions 'Queue' implying asynchronous operation and 'manual-like calculation folder layout' but does not disclose side effects, required state, permission needs, or output behavior. Significant gaps remain.

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 sentence, so it is concise, but it lacks structure. It is appropriately sized for a simple tool but could be more informative without becoming verbose.

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 11 parameters with zero schema descriptions, no annotations, and no output schema, the description is severely incomplete. It fails to explain parameter meanings, return values, prerequisites, or error conditions, leaving agents with insufficient information.

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 coverage is 0%, yet the description adds no explanation for any of the 11 parameters. It does not list or describe cores, quality, forcefield, etc. The description adds no value beyond the parameter names and defaults in the schema.

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 it queues a Forcite GeometryOptimization on the current GUI document, using a specific folder layout. It distinguishes from siblings like ms_gui_dmol3_optimize_current (different engine) and ms_gui_castep_current (different method), but does not explicitly differentiate from other Forcite-related tools.

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?

There is no guidance on when to use this tool versus alternatives. The description implies usage for Forcite optimization on the current document but lacks context on prerequisites, when not to use, or alternative tools for other tasks.

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