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

The description's behavioral content ('Read only; no spend') is fully redundant with the annotations, which already declare readOnlyHint=true and destructiveHint=false. It adds no context beyond the structured fields about auth needs, rate limits, or other operational behavior.

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 but under-specified rather than efficient; it omits essential context while including an opaque reference string ('soclo://tools/soclo_ads_list_ad_account_users') that does not help the agent invoke the tool.

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 tool with six parameters, a nested object, no output schema, and only 50% schema description coverage, the description is far too thin. It leaves required parameter usage, selection context, and behavioral expectations largely unexplained.

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 description provides no meaningful explanation of the six parameters, and schema description coverage is only 50%. Parameters such as accountId, platform, and parameters.businessId are undocumented in both the schema and the description, so the description fails to compensate.

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 restates the title 'Ad account users' without adding a specific verb such as 'list', so it functions largely as a tautology. It does indicate the domain ('Soclo Ads') and safety ('Read only; no spend'), but it does not clearly distinguish this tool from siblings like assign_ad_account_user or remove_ad_account_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?

There is no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The only usage-adjacent signal is 'Read only; no spend', which is a safety property rather than a selection guideline.

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