Create a Slack workspace canvas with markdown content to share structured notes and documentation directly in Slack.
Create a workspace-level canvas with markdown content. Requires canvases:write scope.
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | Canvas title | |
| document_content | Yes | Markdown content for the canvas |
Changes observed during successful MCP inspections.
v0.1.8Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral burden. It discloses the required OAuth scope ('Requires canvases:write scope') and clearly states that the operation creates a new workspace-level canvas. It does not mention response behavior, but the core mutation and permission traits are transparent.
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 front-loaded sentence with no filler. The core action and resource are stated immediately, and the permission requirement is appended efficiently.
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 two-parameter creation tool, the description covers the essential aspects: what is created, at what scope, and what permission is required. It could be more complete by stating what the tool returns, especially since there is no output schema, but the current information is sufficient for basic correct invocation.
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 both parameters. The description only adds 'with markdown content', which restates what the document_content schema description already says. It provides no additional semantic value for either parameter.
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 uses a specific verb ('Create') and a clear resource ('workspace-level canvas'), and specifies that content is markdown. The phrase 'workspace-level' also distinguishes this tool from the sibling create_channel_canvas, making its purpose unambiguous.
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?
The description gives a clear context signal: use this to create a workspace-level canvas rather than a channel-level one. It does not explicitly name alternatives or state when not to use it, but the 'workspace-level' qualifier provides enough differentiation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.