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

While annotations confirm it is a read-only operation, the description adds behavioral context by listing specific attributes returned (`id`, `name`, `needsReauth`), which helps the agent understand the operational state of the connection data.

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?

The tool is described in a single, highly efficient sentence. It front-loads the purpose and efficiently lists all necessary details about the returned data.

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?

Since no output schema exists, the description fulfills the requirement for completeness by explicitly enumerating the key data points the agent can expect to receive upon successful invocation.

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?

Given that the input schema is empty, the description is vital. By listing output fields like `id`, `name`, `category`, and `needsReauth`, it provides semantic meaning to the data the agent will receive, making it maximally useful.

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 clearly identifies the resource (workspace connections/integrations) and provides specific examples of the connection types (Shopify, Gmail, Salesforce), distinguishing it from broader list functions.

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?

It provides a critical usage hint by stating that the returned `id` should be used for subsequent calls to 'other channel tools,' establishing the required operational workflow.

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