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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered; the description goes further by explaining that returned `access` values determine downstream tool choice and that destructive operations delete/archive/overwrite and require per-call user approval. The destructive-approval detail is valuable context beyond the annotations, though it could say more about the shape or size of the returned catalog.

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 the core purpose, then layered rules in a sensible order (mode selection, routing by access, dynamic fields, value reuse, connection preference). It is dense but nearly every clause is actionable; the final UI instruction is slightly tangential to tool invocation but still guides correct behavior.

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, yet the description still explains the meaningful returned fields (`access`, `mine`, dynamic markers) that drive follow-up calls. For a single-parameter discovery tool, an agent has everything needed to call it and act on the result.

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 coverage is 100% for the single `provider` parameter, so baseline is 3; the description adds meaning by specifying that omitting it returns providers and that the value must be reused exactly as returned here. That enforces a correct value contract the schema alone does not convey.

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 opens with a specific verb and resource ('Discover what the workspace's connected integrations can do') and immediately clarifies the two modes: no arguments lists providers, passing `provider` lists that provider's operations with field schemas. It is clearly distinguishable from siblings integration.query, integration.execute and integration.list_options, which are each named and assigned a role.

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?

Explicit routing rules are given: read operations go to integration.query, write/destructive ones to integration.execute, and fields marked `dynamic` require integration.list_options first. It also states a preference rule for `mine: true` connections and a user-facing behavior for multiple matches, leaving nothing to inference.

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