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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so the bar is lower, yet the description still adds real behavioral context: a verified chart_provenance token valid for 15 minutes on any replica, a visibility_probe field on empty search results, and mandatory verbatim attribution footers. That is genuine disclosure beyond the structured fields, though a large share of the text describes the downstream chart_render contract rather than this tool's own behavior.

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?

Purpose is front-loaded in sentence one, but the body is dominated by chart_render/provenance/attribution boilerplate that is largely tangential to invoking this connector, and the attribution paragraph is repetitive ('do not turn it into plain text, invent a URL, or omit it'). Substantial trimming is possible without losing tool-selection value.

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 six-action connector with no output schema, the description covers the domain and output-handling rules but says nothing about return shapes, pagination, or required Slack scopes/permissions for the authenticated user. The per-action semantics live entirely in the schema, which is adequate but leaves the description incomplete as a standalone brief.

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% — the action enum documents each of the six operations and the params object spells out every per-action parameter shape. The description adds no parameter-level detail (no query syntax, thread_ts format, limit defaults), so the 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?

The opening sentence names the resource domain precisely — Slack channels, messages, threads, files, and workspace analytics — which an agent can map to the six enum actions. It never states a verb ('retrieve/list Slack data') and does not explicitly contrast itself with the other ~80 connector siblings, so it stops short of a 5.

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?

Usage is only implied: the agent infers 'call this for Slack workspace questions.' The explicit routing guidance in the text ('call chart_render when the user asks for a visual/trend') concerns a downstream sibling, not when to pick slack_connector over email_connector, crm_connector, or the rest. No exclusions or prerequisites are given.

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