convert_to_slack

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

Annotations declare idempotentHint=true and readOnlyHint=false. Description adds valuable transformation specifics beyond annotations: exact syntax conversions (**→*, _→_, headers→bold, links→<url|text>), helping agents predict output structure. No contradictions with 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 efficiently structured sentences. First sentence establishes purpose and transformation rules; second provides usage context. No redundancy, front-loaded with essential information despite the packed specifics of formatting transformations.

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 100% schema coverage and clear annotations, description adequately covers tool purpose. Absence of output schema noted, but schema's output_path description handles return value documentation. Missing only minor details like maximum input size or complex edge-case handling for completeness.

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%, establishing baseline 3. Description references 'Markdown' input implicitly but does not elaborate on parameter semantics beyond schema descriptions. The output_path behavior is well-documented in schema property descriptions, requiring no additional description text.

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?

Description states specific action ('Convert Markdown to Slack mrkdwn format') and enumerates exact transformations (bold→asterisks, italic→underscores, etc.). Clearly distinguishes from sibling converters like convert_to_html or convert_to_bbcode by specifying Slack-specific mrkdwn syntax.

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?

Explicitly states when to use: 'Use this when pasting formatted content into Slack messages.' Lacks explicit 'when not to use' or named alternatives (e.g., 'use convert_to_html for web instead'), but provides clear contextual trigger.

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