trim_entity

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

With no annotations, the description must disclose behavioral details. It explains that the tool removes part of an entity, indicating a mutating operation, but omits specifics such as how the pick point determines which side to trim, what happens if there is no intersection, or whether the cutting entity is affected. This partial disclosure is insufficient for a destructive 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 sentence, highly concise and front-loaded with the main action. It avoids redundant wording, but its brevity contributes to the lack of parameter and usage details, so it does not achieve a perfect score.

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 destructive nature and the presence of many sibling editing tools, the description is incomplete. It lacks parameter explanations, usage scenarios, and edge-case behavior. The output schema exists but does not compensate for the missing parameter semantics and behavioral details.

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, and the description does not explain the parameters. It says 'cut by the cutting entity' but never maps that to 'cutting_handle', nor does it describe 'pick_x' and 'pick_y'. An agent cannot infer which parameter serves which role from the text alone.

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: removing a portion of an entity at a pick point, with the cutting entity defining the cut. This distinguishes it from broader drawing tools, though it does not explicitly differentiate it from similar editing tools like break_entity or extend_entity.

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?

No guidance is given on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., the cutting entity must intersect the target) or scenarios where this tool is preferred. The description implies a general trimming operation but lacks explicit usage context.

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