slack_workflow_save

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

Annotations indicate idempotent write. Description adds context: local file storage (~/.slack-mcp-workflows.json), hosted brain behavior, and summary_cadence constraints (free vs Pro/Team). This goes beyond annotations.

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?

Two sentences: first states the core action and bindings, second adds storage and behavioral context. Every sentence earns its place with no redundancy.

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 6 parameters, no output schema, and moderate complexity, the description covers purpose, storage, output shape hint, and constraints. Minor gap: no mention of error conditions or permissions.

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 100% with decent descriptions. Description adds some extra context (e.g., workflow_kind determines output shape, summary_cadence limitations) but does not deeply elaborate beyond schema. Baseline 3 is appropriate.

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 clearly states the tool saves or updates a workflow profile, listing the exact bindings (workflow_kind, channels, priority_people, etc.) and the storage location. It distinguishes from siblings like 'slack_workflows' which likely lists workflows.

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 explicit guidance on when to use this tool versus alternatives. It does not mention exclusion criteria or provide context for selecting this tool over siblings.

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