slack_set_channel_topic

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

With no annotations, the description carries the full burden. It only mentions routing through /api/tools/invoke under JWT/tenant/company scope, which is generic. It does not disclose that this tool modifies a channel, requires authorization, or has side effects.

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 short but includes redundant repetition of the tool name. It could be more efficient by omitting the first sentence and front-loading the actual function. It is not lengthy, but the structure wastes space on non-information.

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 simple tool like setting a channel topic, the description is insufficient. It omits what arguments are needed (channel ID, topic text) and does not reference the output schema. An agent would have to guess the required JSON structure.

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?

The input schema has one parameter 'arguments' with no description (0% coverage). The description merely restates 'JSON string of arguments for the connector operation', adding no meaning. The format and expected fields (e.g., channel, topic) are entirely opaque.

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 'Slack connector operation set_channel_topic' essentially restates the name without explaining that it sets the topic of a Slack channel. It does not differentiate from the sibling tool slack_set_channel_purpose. The verb 'set' suggests modification but the resource 'topic' is not clarified.

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 provided on when to use this tool versus alternatives like slack_set_channel_purpose or slack_create_channel. The description does not mention any prerequisites, channel requirements, or expected use cases.

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