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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds two pieces of real context not in annotations: a hard cap of the latest 200 events and the freshness caveat that history is only as current as the last sync — an agent needs both to interpret the result correctly.

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 short sentences, zero filler, with the scope and the 200-event cap front-loaded and the sync-freshness caveat second. Every clause carries information an agent would otherwise lack.

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?

The tool has an output schema, so return shape needn't be described, and annotations cover the safety profile. The description covers the remaining essentials: result cap, scope to one lead, and data-staleness semantics. Nothing needed to call it correctly is missing.

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 must compensate; it only implies lead_id via 'for an LSA lead' and says nothing about business_id or the relationship between the two UUIDs. The parameter names are largely self-describing, so the gap is small, but it is not fully closed.

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 ('Read the latest 200 synced Google LSA conversation events for an LSA lead') and scopes it to a single lead, which separates it from report/account-level siblings like get_lsa_report and get_lsa_account_report. It stops short of naming a sibling as an alternative, but the resource is unambiguous.

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 phrase 'for an LSA lead' implies usage when you have a lead_id and need its conversation history, but the description never states when to prefer this over get_lead, list_lsa_leads, or get_lsa_report, nor any preconditions (e.g. the lead must be synced). Usage is only inferable.

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