Modeling Command

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

The description discloses return behavior (handles for new geometry, mutated targets for in-place) but lacks details on side effects, error states, permissions, or other behavioral traits, with no annotations to augment transparency.

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, front-loaded with purpose, then behavioral differentiation, then aliases, with no unnecessary words.

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 complexity (4 params, nested targets, no output schema), the description covers purpose and aliases but lacks details on target specification, error handling, and return format for all command types.

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 100% schema coverage, the baseline is 3, but the description adds value by enumerating command aliases and clarifying the behavioral difference, going beyond schema descriptions.

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 runs a Cinema 4D modeling operation via SendModelingCommand on target objects, distinguishes between commands that produce new geometry vs in-place mutations, and lists numerous aliases, making it distinct from sibling tools.

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 modeling commands and provides aliases, but does not explicitly state when to use this tool versus alternatives or mention prerequisites, leaving implicit guidance.

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