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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so 'Read only; no spend' largely restates structured data. The description does not explain what the returned status means, whether polling/retry is expected, or how requestId enables recovery — the behaviorally meaningful context for a status tool.

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?

Short and front-loaded with the core action, which is good. But the 'Fields: soclo://tools/...' fragment is unexplained and adds little, while the sentences that would earn their place (polling semantics, statuses) are absent.

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?

This is a nested-parameter, 6-param tool with 50% schema coverage and no output schema, yet the description omits status meanings, polling expectations, and requestId reuse. It is under-specified for the complexity involved.

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 coverage is only 50% across 6 parameters, and the description adds no parameter meaning. 'Fields: soclo://tools/...' is a resource pointer, not clarification of requestId, confirm, or the nested parameters object, 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 specific verb and resource ('Get a bulk request's status'), which is clearer than the name (soclo_ads_get_ad_catalog_batch) suggests. However, it does not distinguish this status-polling tool from sibling status tools like soclo_ads_operation_status, nor from the batch trigger soclo_ads_batch_ad_catalog_products.

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 note but no guidance on when to call this versus other status/operation tools. There is no mention of when it should be used (e.g., after starting a batch) or any exclusions.

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