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

Goes meaningfully beyond the annotations: it discloses that syncing triggers lead ingestion and that existing speed-to-lead configuration may automatically contact newly found leads — an external side effect no annotation can express, and one that materially raises the stakes of a destructiveHint=true, openWorldHint=true operation. It falls short of a 5 because it doesn't address re-sync behavior (whether repeats duplicate leads), part of why idempotentHint is false.

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?

Three short sentences, front-loaded with the action, then the permission gate, then the side-effect warning in descending order of what the agent needs first. No filler or restatement of the title.

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 values need no explanation, and the description covers the two things an agent can't infer from structured fields: the admin permission requirement and the downstream outreach side effect. It is only slightly incomplete in not clarifying what 'sync' does to already-ingested leads or whether it can be safely repeated.

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 full burden for both required UUIDs, but it never mentions business_id or connection_id by name or explains their roles. At best 'explicitly selected connected LSA advertiser' and the admin-role requirement weakly imply a business-plus-connection pairing, leaving the caller to infer which UUID goes where.

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 — sync a connected LSA advertiser — with the added qualifier that it acts on the explicitly selected connection. An agent can distinguish it from the read-only siblings (get_lsa_report, list_lsa_leads) without opening another schema, though no sibling is named as a contrast.

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?

Gives a real prerequisite — 'Requires current business admin role' — which prevents failed calls, and the word 'explicitly selected' hints that the caller must already know which connection to target. However, it never says when to sync versus reading reports or lists, and gives no when-not-to-use or frequency/rate guidance.

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