create_group

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

No annotations are provided, so the description carries the full burden. It says only that items are grouped, without disclosing permissions required, whether the operation is reversible, what happens to existing group membership, or whether board_id must identify an existing board.

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, front-loaded, and free of filler. Its second sentence earns its place by clarifying item_ids, though the overall structure is extremely terse for a mutation tool.

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?

The tool has two required parameters and no annotations, with 0% schema description coverage. Although an output schema exists and need not be explained, the description is incomplete regarding board_id, permissions, and grouping behavior.

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?

Schema description coverage is 0%, so the description must compensate for the undocumented parameters. It clarifies item_ids minimally as 'the items to group,' but does not explain board_id at all, leaving one of two required parameters without added 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 states a clear action, 'Group items together,' which makes the purpose understandable. However, it does not differentiate this create operation from sibling tools such as update_group, ungroup, or get_group_items.

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 create_group versus alternatives like update_group or ungroup. It also omits prerequisites, such as whether items must be ungrouped before being grouped.

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