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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description's "Read only; no spend" reinforces this and usefully adds cost context, but says nothing about scope of accounts returned, pagination, or permissions. Notably, the schema carries a `confirm` flag described as "owner approval of spending/deletion preview," which the description never reconciles with a read-only listing tool.

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 and the operative verb lands first, so there is little waste. But brevity here comes from omission rather than economy, and the trailing documentation-URI sentence consumes space that should have carried actual parameter or return guidance.

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 6-parameter tool with a nested parameters object, one required field, no output schema, and 50% schema coverage, the description is far too thin. It does not say what a returned account record contains, whether results are paginated by `parameters.limit`, or which account the required accountId scopes.

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 only 50% across 6 parameters, and the description contributes no parameter meaning at all. Undocumented fields such as accountId, platform, and parameters.limit are left entirely to the schema, and the odd presence of `confirm` on a read-only list is unexplained. The "Fields: soclo://..." reference is not a substitute for semantics an agent can act on.

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 sentence "List ad accounts" is a clear verb+resource and tells an agent the operation is a non-mutating enumeration. However, it nearly restates the tool name and gives no signal distinguishing it from crowded siblings such as soclo_accounts_list, soclo_ads_get_ad_account_hierarchy, or soclo_ads_list_ad_account_users. The trailing "Fields: soclo://..." pointer supplies no definitional content.

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 use this tool versus soclo_accounts_list or the hierarchy/user-listing siblings, and no prerequisites or exclusions. The agent must infer the selection criteria from the tool name alone.

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