slack_create_canvas

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

No annotations are present, so the description must cover behavioral traits. It only mentions routing through an API and gives no indication of side effects, permissions needed, or whether the operation is destructive. This is a critical gap.

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 not effectively concise. The first sentence is a tautology, the second is routing boilerplate. The Args section is structured but lacks detail. Every sentence does not earn its place as it fails to inform the agent.

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?

Given the tool's complexity (mutation with one parameter and no required fields), the description is grossly incomplete. It does not explain return values (despite having an output schema), behavior, or usage constraints. The agent cannot reliably invoke this tool based on the description alone.

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 schema has 0% description coverage for the single 'arguments' parameter. The description says it is a 'JSON string of arguments for the connector operation,' which adds minimal value beyond the schema's type. It does not explain what keys or values the JSON 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 merely restates the tool name as 'Slack connector operation create_canvas' and gives routing info. It does not explain what creating a canvas means or how it differs from sibling tools like slack_create_conversation_canvas. The purpose is unclear beyond the name.

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 such as slack_create_conversation_canvas or slack_edit_canvas. There are no context or prerequisites mentioned.

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