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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that by disclosing the preview→owner-approved confirm:true flow, requestId reuse for confirmation/outcome recovery, and that the claim only goes live when status is active — exactly the kind of operational behavior an agent needs for a destructive mutation.

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 purpose is front-loaded and the passage is very short with no filler. The trailing 'Fields: soclo://tools/...' pointer is a bit cryptic, but overall it is tight and efficiently ordered.

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 destructive, non-idempotent mutation with a nested payload, 10 params, and no output schema, the description is too thin. It explains the confirm gate but not what the assignment actually does to existing access, what the payload tasks (MANAGE/ADVERTISE/ANALYZE/DRAFT) control, or how the expected* fields factor into the preview/confirm flow.

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?

With 10 parameters at 60% schema coverage and a nested payload object, the description carries real gaps to fill, but it only clarifies the meaning of 'confirm' and 'requestId' indirectly. It leaves payload.userId/payload.tasks, accountId, platform, and the expectedCurrency/expectedBudgetType/expectedBudgetAmount pair unexplained beyond what the schema already shows.

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?

States a specific verb and resource ('Assign a user to an ad account'), which is clearly distinguishable from the sibling soclo_ads_remove_ad_account_user. It doesn't explicitly name or differentiate against list/invite sibling tools, but the core action is unambiguous.

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 implies a gated workflow ('preview, then owner-approved confirm:true with the same requestId'), which is useful usage context, but never states when to choose this tool over alternatives like soclo_ads_invite_ad_account_to_manager or soclo_ads_list_ad_account_users, and offers no exclusions.

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