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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, so 'Read only; no spend' mostly echoes structured data. Nothing is said about what the call returns, whether it is scoped to one business, or handling of pagination, and the 'Fields: soclo://...' pointer is not usable context inline.

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?

It is short, but the brevity comes from omission rather than density, and the trailing URI reference occupies space without conveying meaning to an agent. Under-specification, not conciseness, is the dominant trait.

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?

A nested-parameter, six-argument tool with no output schema needs the description to carry the load, and this one provides nothing about required inputs, return shape, or result scoping. An agent could not reliably call it from this text alone.

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?

Six parameters with only 50% schema coverage and a nested 'parameters' object, yet the description names none of them. businessId (nested, required), platform, adAccountId, requestId and confirm are all left undocumented, so the description fails to compensate for the coverage gap and even leaves the required nested field unexplained.

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 is essentially a restatement of the title 'Business users' with a product prefix, giving no verb or scope beyond what the name already implies. It never says it lists the users of a Meta business, nor how it differs from nearby siblings such as soclo_ads_list_meta_businesses or soclo_ads_list_ad_account_users.

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?

There is no statement of when to call this versus alternatives like soclo_ads_list_meta_businesses or soclo_ads_list_page_users, and no prerequisites (e.g. that a businessId must come from the businesses list). 'Read only; no spend' is the only qualifying hint and it is about safety, not selection.

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