set_bone_property

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

IdempotentHint is provided and not contradicted, but the description adds no behavioral context beyond the property list. It does not mention side effects, prerequisites (e.g., edit mode), or how setting properties like use_connect affects bone hierarchy. With annotations covering idempotency, the description still lacks meaningful behavioral disclosure.

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, front-loaded sentence that immediately states the action and resource, followed by a compact list of allowed properties. Every word earns its place with no filler or redundancy.

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?

Despite having an output schema, the description is incomplete for effective use. It does not specify how to identify the object (armature) and bone, nor does it explain the expected value formats for each property. An agent would need additional knowledge to safely and correctly invoke this tool.

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, the description must compensate, but it only lists property names without explaining their value types or meanings. For example, it does not clarify that head and tail are likely 3-number vectors, roll is numeric, and use_connect is boolean. This leaves critical parameter semantics unresolved.

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 tool sets a bone property and enumerates the specific properties allowed (roll, envelope_distance, head, tail, use_connect), making the action and resource unmistakable. This distinguishes it from sibling tools like set_pose_bone_transform or add_bone.

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 implies use for modifying these bone properties, but provides no explicit 'when to use' or 'when not to use' guidance. It does not mention alternatives or exclusions, such as using set_pose_bone_transform for pose bones, so the usage context is only implicit.

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