organize_objects

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose two useful traits ('group under an empty (moves as one unit)', 'select (highlights for the user)'), but omits any warning that delete is destructive, whether operations are undoable, or the fact that many params (angle, shading, collection, target) only apply to specific actions.

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?

A single compact run-on list; every entry earns its place and the actions are front-loaded. The 'Housekeeping:' prefix adds little, and the run-on form makes the action-to-behavior mapping harder to scan than a structured list, but there is no filler.

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?

For a 7-parameter, 15-action umbrella tool with no annotations and no output schema, the description is a bare action inventory. It never maps params to actions, never flags destructive actions, and gives no return-value or side-effect context, leaving significant gaps for an agent to guess at.

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 57%: name, target, objects, and shading have schema descriptions, while action, angle, and collection have none. The action list in the description maps onto the enum and adds semantic context for group/select/shade, but it does not explain the action-to-parameter coupling an agent needs.

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 enumerates 15 specific operations (rename, join, parent, shade, apply_transform, convert_to_mesh), so an agent knows exactly what the tool does. However it offers no differentiation from overlapping siblings such as transform_object, edit_mesh, or duplicate_pattern, and the 'Housekeeping' label is a mushy category rather than a scope statement.

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 when-to-use guidance and no mention of alternatives, despite clear overlap with transform_object (apply_transform), edit_mesh (join), and duplicate_pattern (duplicate). Nothing tells the agent which of the enumerated actions belong here versus a sibling tool.

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