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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so 'Read only; no spend' merely repeats structured data instead of adding context. Nothing is said about what is returned, whether results are paginated, or what happens when the campaign has no assets.

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 with the operation name, which is good. But the trailing field pointer is opaque clutter that consumes a third of the text without conveying information an agent can act on.

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 six-parameter tool with a nested object, no output schema and a crowded sibling namespace, the description is far too thin. An agent gets no sense of required inputs, return shape, or how to choose this over the adjacent attach/update/remove/list variants.

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?

Six parameters with only 50% schema coverage, and the description adds nothing about them - notably nothing about the required nested parameters.campaignId or the confirm/requestId fields that the schema describes only partially. The 'soclo://tools/...' field pointer does not resolve into usable parameter guidance.

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?

It states a verb and resource ('List campaign assets'), but that is a verbatim restatement of the title, so the agent learns nothing beyond the name. It does not clarify what counts as an 'asset' here (sitelinks, callouts, snippets, media) or how this differs from siblings like soclo_ads_list_ad_group_assets or soclo_ads_attach_campaign_assets.

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 that this is a safe inspection call, but there is no explicit when-to-use, no prerequisite (an accountId and campaignId are required), and no mention of the attach/update/remove campaign-asset siblings that share the same resource.

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