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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantial context they do not carry: the composition of lastSyncSummary (created, updated, unchanged, failed, complete, skipped reasons), what nextAction means, and per-reason remediation for skipped Drive files (shortcuts, unsupported types, >400 MB, trashed, unreadable folders). It also documents the cross-tool identity of connectionId.

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?

Front-loaded with purpose and routing in the first sentences, and every paragraph is information-dense. However, the middle paragraph detailing lastSyncSummary fields and per-reason remediation is heavy relative to the rest and partly overlaps the output schema, which an output schema already exists to describe.

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?

For a zero-parameter, read-only list tool with an output schema, the description covers everything an agent needs: what is listed, what is not listed and where to go instead, the identifier vocabulary shared with sibling tools, and the correct path to actually create a connection. Nothing material 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?

The tool takes zero parameters, so the baseline is 4 and the schema has nothing to explain. The description goes slightly beyond by defining connectionId as 'the provider name used by sync_connections, update_connection_settings, disconnect_connection and get_connect_link', which is genuinely useful interoperability context even though it is not a parameter of this call.

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 ('Lists integrations') and enumerates the covered providers (Google, Search Console, GA4, Drive, analytics, CRM, email, Social publishing, website CMS) plus the returned status fields (health, last sync, failed jobs). It explicitly differentiates itself from list_channels and get_website_cms, so an agent can distinguish it from siblings without opening any schema.

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?

Names alternatives and the conditions that select them: use list_channels to see which social accounts are connected, get_website_cms for the CMS. It also routes the connection workflow ('Connecting still happens in the Mark app — call get_connect_link for the in-app URL, then sync_connections'), giving explicit when-to-use and when-not-to-use guidance.

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