Apply Three.js scene changes

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

Since no annotations are provided, the description must carry the full burden of behavioral disclosure. It mentions 'revision-checked' and 'bounded', but fails to disclose that operations can be destructive (e.g., remove_object, replace_script) or how conflicts are handled. This is insufficient for a tool that can modify or delete scene elements.

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, compact and front-loaded with the verb. Every word adds meaning without redundancy, making it an ideal length for the information it conveys.

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 complex input schema (five operation types, three required parameters) and an output schema, a one-sentence description is inadequate. It lacks details about operation semantics, error conditions, and the output schema, leaving the agent to rely entirely on the schema without high-level 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?

With 0% schema description coverage, the description must compensate for parameter understanding. It adds minimal value: 'scene, script, or project changes' maps loosely to operation types, and 'revision-checked' hints at baseRevision, but it does not explain projectId, baseRevision format, or the operations structure beyond 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 uses a specific verb ('applies') and names the resource ('one revision-checked batch of bounded scene, script, or project changes'), clearly indicating a mutation operation on project content. The phrase 'revision-checked' and 'bounded' distinguishes it from sibling tools like push_project or save_project_copy.

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 no explicit guidance on when to use this tool versus alternatives like push_project or save_project_copy. It implies a revision-checked batch context but does not state exclusions, prerequisites, or when it is preferred over other mutation tools.

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