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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds one scope constraint (it never initiates an import), but says nothing about whether the response is large, whether it is paginated, or whether results are scoped to the given company/environment.

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 with the read scope front-loaded and the exclusion second, which is the right order. The comma-separated bundle of return categories is slightly dense but every item conveys content the agent would otherwise have to discover by calling.

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?

With no output schema, the description usefully enumerates what comes back (previews, progress, counts, errors, destinations), which is the main thing an agent needs. Annotations cover the safety profile. The remaining gap is how company/environment scope the results, which is minor for a read-only list.

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 neither parameter carries documentation. The description does not mention the company or environment parameters at all, leaving the agent to infer from the property names that they scope the read. With low coverage, the description should compensate and does not.

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?

The description uses a specific verb ("Read") and enumerates the resources returned: previews, saved progress, counts, errors, and Summer inbox destinations. It also rules out one adjacent behavior ("Does not start an import"), which separates it from the control sibling. It stops short of naming summer_imports_intercom_preview or summer_imports_intercom_profiles, so the boundary with those siblings is left implicit.

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?

"Does not start an import" implies the agent should choose summer_imports_intercom_control for mutations, which is useful negative guidance. However, there is no positive statement of when this tool should be called versus the preview or profiles siblings, and no mention of what state must exist first (e.g., a preview having been generated).

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