optimize_scene

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

With no annotations, the description carries full burden. It clearly states the modifications (removing orphans, merging vertices) and the return value (log). It could be more transparent about destructiveness or undo capability, but the actions are specific.

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, front-loaded with actions and return value. No extra words, highly concise.

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?

The description covers main actions and return value. Given no output schema, the log return is useful. It could mention scope (entire scene) is clear, but side effects or persistence could be added. Overall adequate for a cleanup tool.

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 description should compensate. The description mentions 'merge duplicate vertices' but does not explain what merge_threshold means (e.g., distance threshold). The parameter name is suggestive but not fully informative for an agent.

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 specific actions: remove orphan meshes/materials/images and merge duplicate vertices on all meshes. It clearly identifies the resource (entire scene) and verb (optimize), and distinguishes from sibling tools like merge_by_distance which only merge vertices, while this tool does a comprehensive cleanup.

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 implies usage for comprehensive scene optimization but does not provide explicit guidance on when to use this tool versus alternatives like merge_by_distance or scene_cleanup. No exclusions or prerequisites are mentioned.

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