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

"Read only; no spend" largely duplicates the annotations (readOnlyHint=true, destructiveHint=false), though "no spend" is a useful clarification in an ads context. Nothing is said about what the returned form contains, whether the formId must belong to the given accountId, or how archived forms behave. The "Fields: soclo://tools/soclo_ads_get_lead_form" pointer is an opaque self-reference rather than behavioral disclosure.

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, but the third fragment ("Fields: soclo://tools/...") conveys nothing actionable and consumes a third of the text. Two of three sentences earn their 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?

For a 6-parameter tool with a nested object, no output schema, and half the parameters undocumented, the description is far too thin. An agent cannot tell what a lead form record looks like, what account scoping is required, or whether confirm/requestId are relevant to this read operation.

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 includes a nested parameters object requiring formId, plus platform and confirm parameters that are undocumented in schema. The description mentions no parameters at all, so it does not compensate for the coverage gap or explain that formId lives inside the nested object.

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?

"Get a lead form" names a verb and a resource, but it is a verbatim restatement of the title and adds nothing. With siblings like soclo_ads_list_lead_forms, soclo_ads_list_form_leads, soclo_ads_list_leads, soclo_ads_create_lead_form and soclo_ads_archive_lead_form in the same namespace, the description does nothing to distinguish retrieving one form from listing them or fetching their leads.

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 list_lead_forms (many forms) or list_form_leads (submissions for a form). The agent must infer the single-vs-list distinction from the tool name alone; no alternatives or prerequisites are mentioned.

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