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' largely restates them rather than adding new information. The description says nothing about pagination (though limit/cursor exist in the schema), rate limits, or whether results are eventually consistent.

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?

Very short and front-loaded, which is good, but the trailing 'Fields: soclo://tools/soclo_ads_list_form_leads' pointer is opaque and consumes a third of the text without conveying usable information.

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?

Six parameters including a nested object, no output schema, and 50% schema coverage — yet the description supplies nothing about required inputs, pagination semantics, or result shape. An agent still has to reverse-engineer the call from the schema alone.

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% and the description adds zero parameter meaning — it never mentions formId, limit, cursor, since, accountId, or the nested parameters object. With half the parameters undocumented in the schema, 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 and resource ('List leads') and narrows scope to 'a single form', which distinguishes it from the sibling soclo_ads_list_leads that presumably spans all leads. It does not name that sibling explicitly, but the form-scoped qualifier is enough for an agent to tell them apart.

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?

There is no statement of when to use this versus soclo_ads_list_leads, soclo_ads_get_lead_form, or soclo_ads_list_local_services_leads. 'Read only; no spend' signals safety but is not usage guidance.

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