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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered elsewhere. The description adds real context beyond that: what fields come back (charge and credit states, source IDs, ratings) and the important distinction between the LSA lead id and the CRM lead_id, which the annotations cannot convey.

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?

Two dense sentences with the purpose front-loaded and the ID-disambiguation note immediately after. Nothing is padded, though the second sentence only matters at consumption time and could have been paired with pagination guidance instead of standing alone.

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?

An output schema exists, so return-format explanation is not owed. However, for a three-parameter listing tool with zero schema descriptions, the description should at least say that business_id scopes the results and that limit/offset paginate them; that gap leaves an agent guessing about call shape.

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 0%, so the description carries the burden of explaining business_id, limit, and offset — and it says nothing about any of them. Pagination semantics (limit max 100, offset max 100000) and the required UUID business_id, which presumably scopes the entire listing, are undocumented in both places.

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 specific verb and resource — listing synced Google LSA leads — and enumerates what the listing carries (charge/credit states, source IDs, rating details), which separates it from the generic list_leads sibling. It never names the sibling explicitly, but 'synced Google LSA leads' is a concrete enough scope for an agent to distinguish it.

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 LSA framing implies when this tool applies versus generic lead tools, and the note that the LSA lead id is what LSA commands consume versus lead_id linking to the CRM is genuinely useful routing information. There is still no explicit when-to-use/when-not statement, no mention of choosing this over list_leads or get_lead, and no prerequisites.

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