markdown_to_list

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

With no annotations, the description carries the full behavioral burden. It discloses the accepted input styles, the parsing scope, and the return format ('list of dicts with 'value' and optional 'status''). It does not describe handling of unsupported markdown, but this is a modest gap for a conversion utility.

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?

Three concise sentences with no fluff. The core action is front-loaded, supported inputs are enumerated in the second sentence, and the return shape is stated in the third. Every sentence contributes.

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 a simple two-parameter converter, the description is nearly complete: it states inputs, supported markdown constructs, and the return shape. The main missing piece is usage guidance relative to markdown_to_canvas and behavior on unsupported input, but the essential calling contract is clear.

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 description coverage is 100%, with content and file_path already described and marked mutually exclusive in the schema. The tool description adds no additional parameter-level meaning, so the baseline score of 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 uses a specific verb ('Convert') with a clear source ('markdown') and target ('Slack List items'), and names the exact constructs it parses (checklists, bullet lists, tables). This distinguishes it from the sibling markdown_to_canvas and other list tools.

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?

The intended use is implied by the description: use this when you have markdown and need Slack List items. However, there is no explicit guidance about when not to use it or why it should be chosen over the closely related sibling markdown_to_canvas.

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