slack_set_channel_topic

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

The description does not contradict the annotations (readOnly=false, idempotent=true, destructive=true) and adds some context: writes require an approval_ref ('Approved platform task UUID when resuming a write') and effect is 'Claimed... Spring verifies it', signaling the agent must assert a write effect. However, the concrete destructive behavior — overwriting a channel's existing topic — is never disclosed. Annotations plus this wrapper context justify a middle score.

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 text is compact and the param lines earn their place given the empty schema. But the opening sentence merely restates the name, and the overall allocation spends its space on platform plumbing (project_id, idempotency_key, approval_ref) rather than on the actual operation contract. Efficient in size, mis-allocated in focus.

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, so return values are documented elsewhere, but the Slack-facing contract is entirely missing: which channel to target, what topic format, and the structure of the `arguments` JSON are undisclosed. For a 7-param tool with zero schema coverage, the description must carry the invocation burden, and it fails to do so for the single parameter that matters most.

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?

With 0% schema description coverage, the param list compensates by glossing each of the 7 fields (e.g., 'idempotency_key: Stable business-action identity', 'project_ref: Exact project correlation reference'). That is useful above the bare schema. But the critical `arguments` param is described only as 'JSON string of arguments for the connector operation' — a black box with no indication of what Slack expects (channel, topic text). The agent cannot construct a valid payload from this.

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 only restates the tool name: 'Slack connector operation `set_channel_topic` (platform tool `slack.set_channel_topic`)'. It never states what the operation actually does — that it updates the topic of a Slack channel. An agent must obtain the purpose entirely from the tool name, making this a tautology.

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 guidance is given on when to use this tool versus siblings such as `slack_set_channel_purpose`, `slack_post_message`, or `slack_get_channel_history`. The sentence 'Routes only through the exact project/account governed connector authority' describes a routing constraint, not a selection criterion. An agent has no basis to choose this over alternatives.

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