add_groups

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

The description explicitly states that groups can reference each other by name within the same call, allowing nested hierarchies. It does not mention error conditions, overwriting behavior, or limits, but since annotations are absent, the description provides the primary behavioral context for bulk creation.

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 two sentences, with the first sentence immediately conveying the core purpose ('Create many bones/groups in one call'). No wasted words; every part adds information.

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 tool with one parameter, no output schema, and no annotations, the description adequately covers the essential behavior: bulk creation, nesting, and parent referencing. It tells the agent how to structure the input to achieve hierarchical results.

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 description covers the groups parameter well, but the tool description adds the critical nuance that parent references can resolve to other groups created in the same call, which is not clear from schema alone. This adds significant value beyond the schema.

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 starts with 'Create many bones/groups in one call', clearly stating the action and object. It distinguishes from 'add_group' (singular) and mentions fast skeleton layout, differentiating from sibling tools like 'add_cubes' which handles cubes.

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 tool description implies it is for batch creation of groups, especially for building nested hierarchies. It doesn't explicitly state when not to use it or provide alternatives, but the context of 'fast way' and parent referencing provides clear guidance for its use case.

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