rhino_scale

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

Annotations only provide readOnlyHint=false, so the description carries the burden. It does not mention that scaling modifies objects in place, whether a copy can be made (despite make_copy parameter), or that object IDs are required. The single sentence lacks behavioral depth.

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 short (one sentence), which is concise, but it omits necessary details that could be included without significant length. It is front-loaded with purpose, but under-specification reduces effectiveness.

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 complexity (non-uniform scaling with center, factors, copy option) and the presence of an output schema (not shown), the description fails to provide enough context for proper invocation. It does not explain how to specify the geometry or behavior, leaving the agent under-informed.

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 schema description coverage 0%, the description adds no parameter information. It does not explain 'centre', the scaling factors, or the make_copy option. The agent must rely solely on the schema, which has limited descriptions for non-nested parameters.

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 resource 'objects', and specifies 'non-uniformly about a centre', distinguishing it from uniform scaling or other transforms. However, it could be more explicit about what non-uniform scaling means (different factors per axis).

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 on when to use this tool vs alternatives like rotate, move, or cage edit. No prerequisites or exclusion conditions provided. The description is purely functional without contextual advice.

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