object.parent

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

The description discloses no behavioral traits beyond the annotations. It does not say whether the operation modifies the scene graph, whether prior parenting is replaced, whether the `keepWorld` option affects transforms, or what side effects occur. 'Risk: standard' and 'maturity: L3' are vague metadata, not behavioral 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 short, but this is under-specification rather than effective conciseness. The sentences about risk, maturity, and generic requirements do not earn their place because they add no actionable information about the tool's core function or parameters.

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 9-parameter scene-graph mutation command, the description is severely incomplete. It fails to explain the parenting operation, required object references, the meaning of `keepWorld`, or how this tool fits with nearby object operations. Even with an output schema present, the missing functional and parameter context leaves the agent unable to invoke the tool correctly.

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 only 33% schema description coverage and no parameter explanations in the description, the key arguments `child`, `parent`, `keepWorld`, `childObjectId`, and `parentObjectId` remain undefined. The description does nothing to compensate for the low schema coverage, so an agent cannot confidently pick between name-based and ID-based object references.

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 only restates the tool name as 'PartMe Blender Harness command `object.parent`' and adds no functional statement about what the command does. It is essentially a tautology; it does not explicitly say that this parents a child object to a parent object, nor does it distinguish the operation from siblings.

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?

There is no guidance on when to use this tool instead of alternatives, no mention of prerequisites such as which object identifiers are required, and no conditions for selecting between `child`/`childObjectId` or `parent`/`parentObjectId`. The 'Requirements' sentence only references generic checks and session policy, not usage context.

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