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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile needs no restating. The description adds genuinely useful context beyond that: a hard 200-event cap and a staleness caveat telling the agent results only reflect previously synced data unless sync_lsa is run.

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 compact sentences that front-load what is returned (latest 200 synced events) before the prerequisite caveat. No redundant restatement of the tool name or title, and every clause adds information.

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 structure need not be described. The description covers scope limit, content, and the sync dependency; the only meaningful gap is the undocumented business_id, which is a schema-side deficiency rather than a description omission.

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% and neither parameter is documented in the schema, so the description must carry the burden. It only weakly implies lead_id via "for an LSA lead" and says nothing about business_id or the UUID format requirements, leaving one of two required identifiers unexplained.

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 (read) and resource (synced Google LSA conversation events for an LSA lead) with an explicit scope limit of 200 events and the content type (customer and advertiser messages). It differentiates itself from generic siblings like get_conversation/list_conversations by tying the resource to LSA leads and to the sync pipeline, though it doesn't name a sibling 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?

"Sync first for current history" implies a prerequisite without naming the sync_lsa sibling or stating when this tool should be chosen over get_conversation. The condition is suggested but not spelled out, so usage is inferable rather than explicit.

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