Group an account into a collection

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

The description discloses important side effects beyond the annotations: 'CREATES the collection if the name is new' and 'Pass an empty collection name to ungroup'. It also adds a CAPABILITY note about draft safety, which is not present in the annotations (readOnlyHint=false only indicates a write operation). This adds meaningful context, though it doesn't fully specify the effect of ungrouping on the collection itself.

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 appropriately sized and front-loaded with the core purpose. Each sentence adds unique information: side effects, downstream usage via schedule_post, parameter guidance, ungroup behavior, and capability context. No wasted words.

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 no output schema, this simple two-parameter tool is fully described. The description covers prerequisites (list_integrations), side effects, usage patterns, and safety/capability notes, making it complete for correct invocation.

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 already provides 100% coverage with descriptions for both 'accountId' and 'collection'. The description adds value by specifying that 'accountId' is from list_integrations and reiterating the ungroup behavior for an empty collection name, slightly enriching the schema's baseline 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 action: 'Group a connected account into a collection' and elaborates that it also creates a collection if the name is new. It differentiates from siblings by explaining the relationship to schedule_post via the 'collection' field, making the tool's role distinct.

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 clear context for when to use the tool: to group accounts, create a collection, or ungroup via empty collection name. It also references list_integrations for the accountId, implying a prerequisite. However, it doesn't explicitly state when not to use it or name alternative grouping tools, so it stops short of a 5.

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