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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered and the description correctly does not contradict it. It adds the returned-id semantics but says nothing about pagination behavior despite limit/offset parameters, nor about auth or rate limits.

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 tight sentences with no filler, front-loading the resource and its returned fields before the ID guidance. The enumeration of return fields is slightly redundant against the output schema, but overall it earns its space.

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 the description need not explain return values, and the ID linkage guidance is a genuine value-add. However, with three undocumented input parameters and no usage boundaries, the definition leaves meaningful gaps for a multi-param list tool.

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% for three parameters, so the description carries the full burden — yet it never explains business_id scoping or the limit/offset pagination semantics. The one thing it does clarify (LSA lead id vs lead_id) relates to output, not to the input parameters.

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 synced Google LSA leads') and even enumerates the returned data (charge/credit states, source IDs, rating details). It implicitly distinguishes itself from the generic list_leads sibling via 'synced Google LSA leads', but never names an alternative explicitly.

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 second sentence gives useful downstream guidance — use the returned LSA lead id for LSA commands and the separate lead_id for the CRM — which is implied usage rather than explicit when-to-use. There is no mention of when to prefer 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.