slack_access_canvas

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false), the description adds meaningful behavioral context: the `effect` parameter is a claimed read/write effect that 'Spring verifies it', `approval_ref` is required 'when resuming a write', and routing is locked to the governed connector authority. This explains how the destructive capability is gated by platform verification and approval, which is exactly the kind of context annotations alone do not convey. No contradiction with annotations.

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 compact and well-organized: a first line naming the operation, a single routing sentence, and a clean bulleted Args list. No filler or redundant restatement of the schema, and the most important scoping constraint is front-loaded near the top.

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?

Combined with the output schema (so return format is covered) and annotations (safety profile), the description adequately explains parameters and write-approval behavior. However, it omits guidance on when to use this governed connector passthrough instead of the dedicated Slack canvas tools, and it leaves the actual operation semantics of `access_canvas` implicit, which an agent needs to invoke it correctly.

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 description carries the full burden and compensates well: every one of the 7 parameters gets a one-line meaning, including the crucial semantics of `effect` (read/write claim verified by Spring) and `approval_ref` (write resumption gate). The main gap is that `arguments` is described only as 'JSON string of arguments for the connector operation', which is somewhat circular and does not reveal what the access_canvas operation's payload should contain.

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 identifies the tool as the Slack connector operation `access_canvas` (platform tool `slack.access_canvas`) and adds the routing constraint, which is more than a tautology of the name. However, it never states what accessing a canvas actually accomplishes functionally (read content? edit? both?), leaving the agent to infer behavior from the name and the `effect` parameter. It does not explicitly distinguish itself from the many canvas-specific siblings like slack_edit_canvas, slack_create_canvas, or slack_canvas_section_lookup.

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 provides no guidance on when to select this tool versus the canvas-specific Slack siblings, and no exclusions or alternatives are named. The only usage signal is the routing constraint ('Routes only through the exact project/account governed connector authority'), which is a prerequisite rather than a decision rule for tool selection.

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