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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so 'Read only; no spend' merely restates structured data. The description adds no behavioral context beyond that: no rate limits, no permission/scope requirements, no explanation of how match quality is computed or how stale the data may be, and the 'Fields: soclo://...' pointer is opaque rather than informative.

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 tool's name, which is good. However, the third sentence is a bare resource URI that conveys nothing an agent can act on, so not every sentence earns its place.

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?

With no output schema, six parameters (two required, one nested), and openWorldHint=true, the description should carry substantial explanatory weight but delivers two short clauses and a pointer. An agent could not confidently predict what it will receive or what destinationId should be.

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% across six parameters including a nested 'parameters' object with a required destinationId. The description says nothing about any parameter — not what destinationId identifies, nor what 'confirm'/'requestId' mean in a read-only context — so it 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 names a verb ('Get') and a resource ('Event Match Quality'), so the general intent is graspable. But 'Event Match Quality' is an undefined domain term with no statement of what entity it is measured on or what the response contains, and nothing distinguishes it from nearby siblings such as soclo_ads_get_ad_tracking_tags or soclo_ads_list_conversion_actions.

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' signals a safe read, but there is no statement of when an agent should call this versus other diagnostics/reporting tools, no prerequisites, and no mention of what accountId/destinationId must refer to. The agent is left to infer usage entirely.

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