convert_to_textile

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

Annotations declare idempotentHint=true and destructiveHint=false. Description adds platform compatibility context but does not disclose behavioral traits like 'creates parent directories automatically' (described in schema) or whether conversions are lossy.

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, zero waste. First sentence establishes core function; second provides platform context. Every element earns its place.

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?

Appropriate for a conversion utility with 2 parameters and high schema coverage. Output behavior is well-documented in schema (string vs file return). Platform mention adds necessary domain context.

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 detailed descriptions for both parameters. Description does not add parameter semantics beyond schema, so baseline 3 applies per scoring rules for high-coverage schemas.

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?

Specific verb 'Convert' with clear source/target resources (Markdown to Textile). Distinguishes from siblings by naming the specific markup format (Textile vs HTML, AsciiDoc, etc. in the convert_to_* family).

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?

Provides contextual guidance by listing specific platforms (Redmine, Basecamp, CMS) that consume Textile, implicitly signaling when to use this tool. Lacks explicit 'when not to use' or comparison with alternatives like convert_to_html.

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