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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the 'Read only; no spend' sentence largely restates structured data. The remaining content, 'Fields: soclo://tools/soclo_ads_get_ad_audience,' is a dangling pointer that never explains what is returned, whether audienceId must exist, or how errors surface.

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-loads the verb+resource, which is good, but the third sentence is a wasted dangling URI reference that conveys no actionable information. Brief, though not because 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?

This tool has no output schema, so the description should explain the return shape — and it doesn't; 'Fields: soclo://...' is not a substitute. Combined with 6 params at 50% coverage and a nested object, an agent lacks what it needs to call this correctly.

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 50% across 6 parameters including a nested params object, and the description adds nothing: it never mentions accountId, the required nested audienceId, or the confirm/requestId semantics. With half the parameters undocumented, the description needed to compensate and does not.

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+resource ('Get audience details') that an agent can map to a single audience record. It does not explicitly distinguish itself from the adjacent siblings soclo_ads_list_ad_audiences, soclo_ads_update_ad_audience, or soclo_ads_delete_ad_audience, so sibling differentiation is only implied by the verb 'Get'.

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?

The only guidance is the fragment 'Read only; no spend,' which hints that this is a non-costly read but never states when to prefer it over list_ad_audiences (all audiences) or update_ad_audience (mutating). No explicit when/when-not or alternative routing is given.

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