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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the trailing "Read only" adds nothing new. The useful addition is the disclosure of what each lead record contains (emails, follow-ups, drafts, state), though pagination, ordering, and result-size behavior remain unstated.

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?

A single sentence with the resource and its contents front-loaded, no filler. The only waste is the redundant "Read only" clause, which restates an annotation the agent already has.

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?

With no parameters and no output schema, the description does most of the work and covers the return payload reasonably well. It is still silent on result volume, ordering, and how this listing differs from the many lead-related siblings, which an agent needs to select it confidently.

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?

The tool takes zero parameters, so the baseline of 4 applies. There is nothing for the description to disambiguate, and it correctly does not invent parameter guidance.

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 the owner's leads") and enumerates the payload (emails, follow-ups, LinkedIn drafts, per-lead state), so an agent knows what comes back. It does not differentiate from nearby siblings such as soclo_leads_get, soclo_leads_find, or soclo_ads_list_leads, leaving the listing-vs-searching boundary implied.

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 possessive scoping ("the owner's leads") implies bulk retrieval of all leads, which hints at when this beats a targeted lookup. However, there is no explicit statement of when to use this versus soclo_leads_find or soclo_leads_get, 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.