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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description's 'no spend' reinforces that but adds little else — nothing about result volume, rate limits, or what a generated idea set looks like. It is consistent with the annotations, not contradictory.

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-loaded, which is good, but the third sentence is a bare pointer ('Fields: soclo://tools/...') that conveys no usable information to an agent. It is concise but under-informative rather than efficient.

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 10-parameter, nested-payload tool with no output schema, the description should at minimum explain which seed inputs are required and what is returned. It leaves the agent to reverse-engineer the payload structure from the schema alone, which is insufficient given the nested object.

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 10 parameters, a nested payload object, and only 60% schema description coverage, the description contributes nothing about seedKeywords, seedUrl, countries, network, or pageSize. The nested payload fields (the actual idea-generation inputs) are entirely undocumented, 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?

The description states a specific verb and resource ('Generate keyword ideas') within the Soclo Ads domain, so the purpose is unambiguous. It does not, however, distinguish itself from the closely related sibling soclo_ads_generate_keyword_historical_metrics, which an agent could easily confuse it with.

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?

'Read only; no spend' gives a safety cue but no guidance on when to choose this over soclo_ads_generate_keyword_historical_metrics or the many keyword-list tools. There is no mention of prerequisites such as needing seed keywords or a seed URL before calling.

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