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 "Read only; no spend" merely restates what structured data already says. Nothing is added about result shape, pagination behavior, or whether labels are scoped to the account or platform.

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 front-loaded with the purpose, which is good, but the trailing "Fields: soclo://tools/soclo_ads_list_ad_labels" is an opaque self-reference that consumes space without conveying meaning to an agent.

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 six-parameter list tool with no output schema and half the params undocumented, the description is too thin: it omits pagination semantics, the meaning of platform vs adAccountId, and what the caller gets back. The annotations cover safety but not the operational details an agent needs.

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 six parameters and only 50% schema description coverage, the description should compensate but says nothing about any parameter — not accountId, platform, adAccountId, or the nested parameters.after/limit pagination fields. The cryptic "Fields: soclo://tools/..." pointer is not usable parameter guidance.

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 ("List ad labels") that clearly maps to a read operation, and the name/title reinforce it. It doesn't explicitly distinguish itself from the many sibling label tools (create_ad_label, update_ad_label, attach_ad_label, remove_ad_label), but the verb alone makes the distinction fairly obvious.

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 alternatives, no prerequisites, and no mention of pagination or when to reach for attach/remove label instead. "Read only; no spend" hints at a safe context but gives no routing guidance.

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