create_account_group

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the mutation profile is covered structurally. The description adds the outcome concept (a reusable target set for posts) but says nothing about name uniqueness, error behavior on duplicates, or required permissions, which matters for a non-idempotent create.

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?

A single sentence that front-loads the action and follows with a concrete example and the reason it matters. No filler, no restatement of the tool name.

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 five-parameter create tool with annotations covering safety and no output schema, the description covers what is created and why. It leaves return-value expectations (e.g. whether a new group ID comes back) and duplicate-name behavior unstated, but that is a modest gap given the structured coverage.

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 80%, so the schema documents name, color, isDefault and connectionIds on its own. The description reinforces 'named' and the connection-bundling intent, but the undocumented 'description' parameter receives no clarification and no format or constraint details are added.

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 gives a specific verb and resource ('Create a named account group') and explains the resulting behavior ('bundling social connections, so future posts can target the whole set at once'). The 'Create' verb naturally separates it from update_account_group and add_connections_to_group, though no sibling is named explicitly.

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?

Usage is only implied through the stated benefit of grouping connections for targeting. There is no guidance on when to create a new group versus adding connections to an existing one via add_connections_to_group, and no mention of prerequisites like available connection IDs from list_connections beyond the schema hint.

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