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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false. The description adds one useful non-annotation nuance: discovery happens without mutating the MCP tool list ('so the catalog can grow without an MCP reload'). It does not disclose that side effects depend entirely on the target slug, nor auth/error behavior, so it remains a modest addition.

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 tight sentences, front-loaded with the action and the identifier source. The trailing clause about the catalog growing is slightly tangential but still informative, so it earns its place.

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 tool that can execute an arbitrary connected integration with unpredictable side effects and no output schema, the description covers the mechanics but omits return shape, failure modes, and the fact that behavior is fully determined by the target slug. Adequate but with clear gaps.

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 100%, so the schema already documents all three parameters including the nested 'arguments' object and the in_workspace override. The description adds only the slug-format/source hint, which the schema already restates; baseline 3 is correct.

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 ('Run') plus the resource ('a connected integration tool') and pins down the exact identifier format (ext<id>_<name> slug). It also names the sibling tool that produces that slug (integrations_search_tools), so an agent can distinguish it from search/get-schema siblings without opening a 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?

It clearly tells the agent where the required tool_name comes from ('from integrations_search_tools') and that arguments are the target tool's own arguments. It gives clear usage context but states no explicit when-not or alternative (e.g. integrations_get_tool_schema to inspect first).

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