slack_delete_canvas

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

Annotations already carry destructiveHint=true and idempotentHint=true, and the description adds useful context about idempotency keys, claimed effect verification, and approval_ref being needed when resuming a write. It still does not describe the deletion behavior itself (e.g., reversibility, cascading effects) beyond what the annotations imply.

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 bulk of the description is a compact, readable Args block. The first sentence is redundant, restating both the tool name and platform tool name, and the routing sentence is useful but placed before any statement of what the operation does.

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 destructive connector operation with an opaque `arguments` payload and zero required parameters, the description omits essential context about what resource is targeted, what valid arguments look like, and how the result is reported. The presence of an output schema reduces the need to explain return values, but not the need to explain operation semantics.

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 Args block is the only parameter documentation, and it gives glosses for all seven parameters. However, the central `arguments` parameter is only described as 'JSON string of arguments for the connector operation'—a circular explanation that omits the actual Slack delete_canvas payload, so the agent cannot determine what identifiers are needed.

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 a specific Slack connector operation, `delete_canvas`, and names the platform tool, so the verb/resource is inferable. However, it never states in plain terms that this deletes a Slack canvas, and it does nothing to distinguish the operation from siblings like `slack_edit_canvas` or `slack_access_canvas`.

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?

There is no guidance about when to use this tool versus alternatives; the only contextual statement is that it 'routes only through the exact project/account governed connector authority,' which is a routing constraint, not a selection rule. The description neither explains prerequisites nor excludes cases where another Slack tool should be used.

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