scale_body

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

Without annotations, the description should disclose that scaling modifies bodies in-place and is destructive. It only mentions scaling uniformly or non-uniformly and default base point, but lacks behavioral details like coordinate system or permanence.

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 that efficiently conveys the tool's function without 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?

For a tool with 6 parameters and no output schema, the description is brief. It covers the two scaling modes and default base point, but lacks information on return value, error handling, or behavior when scaling multiple bodies.

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 coverage is 100% so baseline is 3. The description adds value by clarifying that scale_factor is overridden by scale_x/y/z, which helps understand parameter precedence.

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 action (scale) and resource (bodies), and specifies two modes (uniformly or non-uniformly), distinguishing it from sibling tools like move_body or mirror.

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 does not provide explicit guidance on when to use this tool versus alternatives, such as when to use non-uniform vs uniform scaling, or prerequisites like body selection.

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