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 the safety profile is fully covered structurally. The description's 'Read only; no spend' restates this but adds the useful 'no spend' assurance in a spend-sensitive ads context. It says nothing about pagination behavior, rate limits, or what the openWorld external call returns.

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 purpose, which is good. But the third fragment ('Fields: soclo://tools/soclo_ads_list_lead_forms') is an unresolvable reference that consumes space without conveying anything actionable.

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 tool with a required accountId, a nested parameters object with cursor-based pagination, and a confirm/requestId confirmation protocol, the description covers almost none of that. With no output schema, the agent also has no idea what a lead form record contains, and the description does not fill that gap.

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 description coverage, and the description adds no parameter meaning at all — nothing on accountId vs adAccountId, platform, the nested parameters.limit/cursor pagination, or when the confirm/requestId confirmation flow applies. The cryptic 'Fields: soclo://tools/...' pointer is not usable semantics.

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 concrete verb and resource ('List lead forms'), so an agent knows the operation type and target object. It does not differentiate this tool from nearby siblings such as soclo_ads_list_form_leads, soclo_ads_list_leads, or soclo_ads_get_lead_form, which is exactly the ambiguity that matters here.

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 it is a retrieval tool, which implicitly contrasts with create_lead_form/archive_lead_form, but no explicit when-to-use, prerequisites, or alternative routing is given. The agent gets no guidance on how to choose between this and the several other lead-listing siblings.

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