Connect Slack ops bridge

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

Annotations already declare readOnlyHint: false, destructiveHint: false, and openWorldHint: true, so the mutation/non-destructive safety profile is known. The description adds context about what the scaffold contains (adapter, alert rows, approval-gated commands, safety notes) but doesn't disclose any side effects, permissions, or reversibility beyond the annotations. This is acceptable but adds only moderate value.

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 description is a single, dense sentence with no wasted words. It front-loads the main purpose ('Create a Slack operator-alert scaffold') and then lists the included components. Every phrase adds value, and it is appropriately concise for the tool's complexity.

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?

Given 11 parameters, no output schema, and mutation annotations, the description is incomplete. It does not describe the return value, side effects, how the scaffold integrates with the project, or the significance of key parameters like channel_name or adapter_mode. While the scaffold composition is mentioned, essential operational context for an agent to invoke the tool correctly 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?

Schema description coverage is very low (18%: only 'name' and 'parent_path' have descriptions). The description mentions 'webhook/socket adapter', 'alert rows', 'approval-gated command rows', and 'token/signing safety notes' which loosely map to parameters like adapter_mode/socket_url, alert_count, approval_required/command_count, but it does not explain the meaning of most parameters (active, channel_name, workspace_label, etc.) or their expected values. The description does not compensate adequately for the lack of schema documentation.

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 states the tool will 'Create a Slack operator-alert scaffold' with specific components (webhook/socket adapter, alert rows, approval-gated command rows, token/signing safety notes). The verb 'Create' plus the resource 'Slack operator-alert scaffold' is specific and distinguishes this from sibling connect_* tools like connect_qlab_cue_stack or connect_webrtc_browser_input by focusing on Slack and alert scaffolding.

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?

No usage guidance is provided. The description does not indicate when to use this tool vs. alternatives (e.g., other connect_* bridges), nor does it mention prerequisites or exclusions. There is no 'use this when...' or 'for other integrations, see...' phrasing.

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