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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The phrase 'Read only; no spend' largely restates that, though 'no spend' usefully reassures on cost. Nothing is said about pagination, result volume, or rate limits for this open-world call.

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?

The core sentence is tight and front-loaded, which is good. But the trailing 'Fields: soclo://tools/soclo_ads_list_leads' fragment is opaque and occupies space that could have documented filtering or pagination.

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 six-parameter, nested-object, open-world listing tool with no output schema, the description should explain pagination (cursor/limit), the time filter (since), and the form scoping (formId). None of that appears, leaving the agent to guess at the most consequential controls.

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 six parameters exist, including a nested 'parameters' object whose limit/since/cursor/formId fields carry no descriptions at all. The description adds no meaning to accountId, platform, adAccountId, or the nested filter fields, 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?

States a specific verb and resource: 'List submitted leads', so the agent knows it is a read/lister operation. However, the sibling list contains near-neighbors (soclo_ads_list_form_leads, soclo_ads_list_lead_forms, soclo_leads_list) and the description makes no effort to distinguish this tool from them.

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' gives a lightweight cue that this is a safe retrieval operation, and the name implies when it applies. But there is no explicit guidance on when to pick this over soclo_ads_list_form_leads or soclo_leads_list, and no prerequisites or exclusions are given.

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