slack_delete_canvas

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

The description only mentions routing and authentication scope. It does not disclose whether deletion is permanent, whether it requires confirmation, or error handling for non-existent canvases.

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 brief (3 sentences) but lacks substantive guidance for an agent. It includes routing details that may be redundant in context.

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?

Despite having an output schema, no explanation of return values. No comparison to sibling tools. Critical usage details (what must be in the arguments JSON) are missing.

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 single parameter 'arguments' is described only as a JSON string for the connector operation, with no details on required fields (e.g., canvas_id) or format. Schema coverage is 0%.

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 name and description state this deletes a Slack canvas, but no details on exactly what constitutes a canvas or how it differs from similar operations like slack_edit_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?

No guidance on when to use this tool versus alternative canvas operations (create, edit, access). No prerequisites or context for deletion.

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