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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so 'Read only; no spend' merely restates what is structured. The description adds no new behavioral context such as what a catalog contains, whether the lookup requires an existing catalogId, or scope/rate constraints.

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, which is good, but the 'Fields: soclo://tools/soclo_ads_get_ad_catalog.' sentence is an opaque pointer rather than usable information. Brevity here is achieved by omission rather than efficiency.

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 object and no output schema, the description is far too thin. It does not explain what a product catalog is, which identifier fields are required, or what the call returns, leaving major gaps for the agent.

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 only 50% schema description coverage and a nested 'parameters' object, the description must compensate, but it provides zero parameter meaning beyond a 'soclo://tools/...' URI pointer. Undocumented fields like accountId, platform, and the catalogId/catalogAccountId nesting are left for the agent to guess.

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 a product catalog'), and the singular form weakly implies a single-record fetch versus a list. However, it does nothing to distinguish it from closely named siblings like soclo_ads_list_ad_catalogs, soclo_ads_get_ad_catalog_batch, or soclo_ads_list_ad_catalog_products, leaving the agent to infer the distinction from the name alone.

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' hints at a safe read context but gives no guidance on when to choose this over the list/batch catalog siblings. No prerequisites, no exclusions, no alternatives are named.

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