simplify_mesh_model

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

With no annotations, the description must carry the transparency burden. It discloses the decimation algorithm and that the result is lower-resolution. However, it does not mention whether the operation is destructive to the original file, required permissions, or potential side effects like loss of detail. The default output path suggests non-destructive behavior but is not explicit.

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 concise and front-loaded with the purpose. It includes algorithm details and parameter documentation without fluff. The structure could be slightly improved by separating parameter descriptions more clearly, but overall it is efficient.

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 simplicity of the tool (3 parameters, no nested objects), the description covers key aspects: purpose, algorithm, parameters, return value. It lacks error handling or invalid input behavior, but for a straightforward tool it is reasonably complete.

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?

The input schema has 0% description coverage, so the description must compensate. It provides clear, detailed parameter descriptions: file_path (STL file), target_ratio (fraction 0.01-1.0), and output_path (default to <name>_simplified.stl). This adds significant meaning beyond the bare schema properties.

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 tool's function: 'Reduce mesh triangle count for faster preview or smaller files.' It specifies the algorithm used (vertex-clustering decimation) and the outcome (lower-resolution version of same shape). This distinguishes it from sibling tools like repair_mesh or hollow_mesh_model.

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 use cases ('faster preview or smaller files') but does not provide explicit guidance on when to use this tool versus alternatives in the extensive sibling list. No when-not-to-use or prerequisite information is given.

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