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

Annotations already declare destructive/openWorld behavior, but the description adds useful workflow context: a preview-then-confirm sequence, requestId reuse, and a condition that the claim is live only when status is active. This is additional value beyond the structured hints, though it still does not explain exactly what access is granted or revoked.

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 and front-loads the purpose, with no wasted sentences. The 'Fields: soclo://...' reference and 'Claim live only when status is active' are somewhat cryptic but do not bloat the text.

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 10-parameter nested mutation, the description covers the critical confirmation workflow but omits parameter-level detail, alternative-tool guidance, and any post-confirmation status/recovery explanation beyond the requestId hint.

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 60%, and the description only echoes the confirm and requestId workflows already documented in the schema. It adds no meaning for pageId, userId, businessId, tasks, accountId, or the expected* preview fields.

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 specific verb and resource: 'Assign a user to a Page.' It is clear what the tool does, but it does not distinguish this tool from nearby siblings such as soclo_ads_assign_ad_account_user or soclo_ads_remove_page_user.

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?

It gives procedural guidance ('preview, then owner-approved confirm:true with the same requestId') but does not say when to use this tool versus alternatives, nor does it mention prerequisites such as listing existing page users first.

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