set_transform

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Set' implies a mutation operation, but it doesn't specify whether this requires specific permissions, if changes are reversible, what happens to unspecified transform components, or any rate limits. The description lacks critical behavioral context for a mutation tool with zero annotation coverage.

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 extremely concise at four words, with no wasted language. It's front-loaded with the core action and target. However, this brevity borders on under-specification, as it omits necessary details for a tool with multiple parameters and no annotations.

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 a mutation tool with 5 parameters, 0% schema description coverage, no annotations, and an output schema (which reduces need to describe returns), the description is incomplete. It doesn't clarify the tool's role among siblings, parameter meanings, or behavioral traits, leaving significant gaps for an agent to use it correctly in a 3D/scene manipulation context.

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 0% schema description coverage for 5 parameters, the description adds minimal value beyond the schema. It mentions 'transform values', which hints at parameters like location, rotation, and scale, but doesn't explain their semantics (e.g., coordinate systems, units, array formats) or the purpose of 'name' and 'space'. This fails to compensate for the schema's lack of 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 'Set object transform values' clearly states the action (set) and target (object transform values), but it's vague about what 'transform values' specifically entail. It doesn't distinguish this tool from potential siblings like 'select_objects' or 'create_primitive', leaving ambiguity about its specific role in the 3D/scene context.

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 no guidance on when to use this tool versus alternatives. With siblings like 'select_objects', 'create_primitive', and 'execute_ops', there's no indication of whether this is for modifying existing objects, initializing new ones, or other scenarios. No prerequisites, exclusions, or contextual recommendations are mentioned.

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