slack_edit_canvas

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

With no annotations present, the description must disclose behavioral traits such as idempotency, destructiveness, or authorization requirements. It only states that the tool routes through an API endpoint under standard credentials, which is generic and uninformative. The agent cannot determine if editing a canvas is reversible or what side effects occur.

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 but not optimally front-loaded. The first sentence is a formal restatement of the tool name, which wastes space. The routing information ('Routes through /api/tools/invoke...') is low-value and could be omitted. The structure includes an 'Args' section, but the content is sparse. It could be both shorter and more informative.

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 an edit operation, the description is critically incomplete. It does not confirm that the tool modifies an existing canvas, specify which attributes can be edited, or note any constraints (e.g., canvas ownership or permissions). Even though an output schema exists, the lack of input context makes it difficult for the agent to use the tool 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?

The single parameter 'arguments' is described as a 'JSON string of arguments for the connector operation', which adds minimal value. Since the input schema has 0% description coverage, the description should compensate by listing expected fields or providing an example structure, but it does not. The parameter remains a black box, forcing the agent to guess its contents.

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 repeats the tool name as 'edit_canvas' and labels it as a 'Slack connector operation' without specifying what editing a canvas entails (e.g., content, properties, collaborators). It fails to distinguish the action from siblings like slack_create_canvas or slack_delete_canvas, leaving the agent to infer purpose from the name alone.

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 alternative Slack canvas operations. There is no mention of prerequisites, typical use cases, or scenarios where a different tool (e.g., slack_canvas_section_lookup) would be more appropriate. The description only contains technical routing details that do not aid in decision-making.

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