scale_entity

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It describes the basic scaling action but omits important details such as whether the operation is destructive, reversible, or affects child objects. No side effects or constraints are mentioned.

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 very concise, consisting of a single sentence that efficiently conveys the essential information. It is front-loaded and free of extraneous text, though it could be slightly more structured for clarity.

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 simplicity (3 parameters, no output schema), the description is adequate but not thorough. It explains the two scaling modes but does not discuss the origin parameter's behavior, entity applicability, or potential side effects. Some context is missing, making it minimally 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?

Schema description coverage is 100%, so baseline is 3. The description adds value for the 'scale' parameter by explaining its two forms (number vs array), but it does not elaborate on 'origin' or 'entity_id' beyond what the schema already provides. Overall, some added meaning but limited.

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 verb 'Scale' and the resource 'an entity', and it distinguishes between uniform and non-uniform scaling. However, it does not specify which entity types are supported (e.g., components, groups, faces), leaving some ambiguity among sibling tools like 'move_entity' and 'rotate_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?

The description provides clear usage instructions for providing a single number or an array for scaling. However, it does not offer explicit guidance on when to use this tool versus alternatives like 'move_entity' or 'rotate_entity', nor does it mention prerequisites or context.

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