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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false. The description merely repeats 'Read only; no spend' and adds no further behavioral context such as what the hierarchy contains, how deep it goes, or any external system dependency implied by openWorldHint.

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 and front-loads the purpose, but the final sentence ('Fields: soclo://tools/soclo_ads_get_ad_account_hierarchy') is a non-informative pointer that does not earn its place. The middle sentence is largely redundant with annotations.

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?

Given six parameters, a nested object, 50% schema description coverage, and no output schema, the description is far too thin to guide correct invocation. It does not explain what the hierarchy returns, how accountId differs from adAccountId, or what the confirm/requestId parameters are for in this read-only call.

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%, with the required accountId lacking any description and platform/parameters undocumented. The tool description provides zero parameter meaning, instead pointing to an internal URI ('soclo://tools/...') that does not help an agent understand the six parameters.

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 ('Get manager account hierarchy'), making the basic purpose clear. However, it does not differentiate this tool from related siblings such as soclo_ads_get_ad_tree or soclo_ads_list_ad_accounts, so an agent cannot tell when this hierarchy view is preferable.

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?

The description gives no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or appropriate contexts. The note 'Read only; no spend' is a safety characterization, not usage guidance.

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