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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description's 'Read only; no spend' is largely a restatement. It adds no context about the returned tree shape, pagination, or how the confirm/requestId flow applies to a read operation.

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, but the 'Soclo Ads:' prefix is redundant and the trailing 'Fields:' URI contributes no actionable information, leaving only two meaningful fragments.

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 a nested 17-field parameter object and no output schema, the description should explain the tree returned and how the filter parameters shape it. It says nothing about either, so an agent has no basis for calling it correctly beyond the required accountId.

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%, and the required accountId, platform, and the entire nested parameters object (page, sort, status, dailyLevel, fromDate, etc.) carry no descriptions in either schema or description. 'Fields: soclo://tools/soclo_ads_get_ad_tree' is a pointer, not parameter meaning, so the description fails to compensate for the coverage gap.

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?

States a verb and resource ('Get campaign tree'), which is more specific than a bare name restatement, but does not distinguish it from the many nearby read siblings such as soclo_ads_list_ad_campaigns, soclo_ads_get_ad_campaign_details, or soclo_ads_get_ad_account_hierarchy. An agent cannot tell which of these returns the hierarchical campaign/adset/ad structure.

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 when-to-use guidance, no named alternative, and no exclusions. 'Read only; no spend' hints at cost safety but does not say when to reach for the tree versus a flat campaign list or a details call.

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