ms_gui_apply_current

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. The description mentions 'queues' (implying asynchronous operation) and 'modifies in place', but does not elaborate on destructive potential, authentication requirements, rate limits, or what happens to the document state. This is insufficient for a tool that modifies the GUI.

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 consists of two sentences and is front-loaded with the core purpose. It is concise with no redundant information. However, the brevity sacrifices completeness for a tool with six parameters.

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 the tool's complexity (6 parameters, no output schema, no annotations), the description is far from complete. It does not explain return values, side effects, or parameter usage. The agent cannot fully understand how to invoke the tool correctly without additional context.

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 only 17%, meaning the description adds no value for most parameters. The tool description does not explain any parameter beyond what the schema already provides for 'body'. With 6 parameters (1 required) and no parameter descriptions in the description itself, the agent lacks essential semantic guidance.

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 verb 'queue' and the resource 'MaterialsScript body that modifies the current GUI document'. It provides an example use case ('on this molecule...' edits), making the purpose clear. However, it does not explicitly differentiate from sibling tools like ms_gui_create_current or ms_gui_edit_current.

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 includes guidance to 'Use this for 'on this molecule...' edits', implying a context for use. However, it does not specify when not to use this tool, nor does it mention alternatives among the many sibling GUI tools. The usage context is implied but not exhaustive.

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