create_armature

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

The description discloses that bones are created in edit mode and switched back to object mode, which is a useful behavioral detail not evident from annotations or schema. No annotations exist, so the description adds value.

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 three sentences: purpose, bone format, and mode behavior. Every sentence adds value with no 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?

Given the tool's complexity, it explains the bone format and mode, but lacks details on default behavior when name or bones are null, error handling, or return values. Acceptable but not comprehensive.

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?

The schema has 0% description coverage, so the description completely carries the burden. It explains the expected structure for the 'bones' parameter (list of dicts with name, head, tail, parent) and notes that parent is optional, adding crucial meaning.

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 creates an armature with bones for rigging. However, it does not distinguish itself from the sibling tool 'armature_create', which likely has a similar purpose.

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 is provided on when to use this tool versus the many related armature tools (e.g., armature_add_bone, armature_create). The description only gives the bone dict format but no context for tool selection.

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