slack_access_canvas

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

No annotations provided, so description carries full burden. It mentions routing and auth scope but does not disclose whether the operation is read-only, modifies state, what side effects occur, or any permissions needed. The name 'access' suggests read, but not explicit.

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 (three lines) and concise, but the structure is poor. It leads with a generic connector operation label before stating the actual purpose. The routing details could be secondary.

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, the description does not mention what the tool returns. Given sibling tools for canvas, the lack of differentiation and output description makes it incomplete for an agent to use effectively.

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 coverage is 0% and the description only repeats the schema parameter: 'Args: arguments: JSON string of arguments for the connector operation.' It adds no information about what fields the JSON should contain, leaving the agent guessing.

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 says 'Slack connector operation access_canvas' but fails to explain what accessing a canvas means or what the tool actually does. Among siblings like slack_canvas_section_lookup, slack_create_canvas, etc., there is no distinction. The name implies retrieval, but the description does not confirm.

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 other canvas-related tools (e.g., slack_canvas_section_lookup, slack_create_canvas). No context for when to invoke it or prerequisites.

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