ms_gui_model_current

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Queue' suggests asynchronous submission, and 'without creating a new document' is a useful side-effect note, but the description does not disclose whether the operation mutates the document, whether a document must already be open, what documentName does, or what the result of queuing is. This is a significant transparency gap for a tool that performs an operation.

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, front-loaded sentence with no wasted words. It states the action, the target scope, example operations, and a key exclusion—'without creating a new document'—all in one compact sentence.

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?

Despite having five parameters, no annotations, and no output schema, the description omits most of the behavioral and parameter detail an agent needs to invoke this tool correctly. It identifies the operation family and document scope, but not the meaning or expected values of several parameters, nor the side effects of queuing the operation.

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 all five parameters. It only hints at the 'operation' parameter by naming Clean and AdjustHydrogen, and it partially clarifies documentName through 'current GUI document.' It does not explain exportFile, ballAndStick, or cleanIterations at all, leaving most parameters semantically opaque.

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 states a clear verb and resource: 'Queue a basic Materials Studio modeling-toolbar operation on the current GUI document.' It names concrete examples (Clean, AdjustHydrogen) and explicitly notes it does not create a new document, which helps differentiate it from document-creation siblings. It is slightly vague about what counts as a 'basic' operation, but the examples anchor it well.

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 clear context: use this for basic modeling-toolbar operations on the current GUI document, and it explicitly excludes creating a new document. It does not name sibling tools or state when to prefer them, but the 'current document' and 'without creating a new document' constraints provide useful selection guidance.

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