convert_to_bbcode

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

Annotations establish safety profile (idempotent, non-destructive). The description adds valuable behavioral context by enumerating the specific BBCode tags supported and target forum platforms, which is critical information not present in structured fields.

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 tightly constructed sentences with zero waste: first establishes conversion direction, second details supported formatting tags, third provides platform context. Front-loaded with the essential action.

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 comprehensive annotations, the description adequately covers the conversion domain. Mention of specific BBCode tags and forum platforms provides sufficient context. Could benefit from explicit mention of dual return modes (string vs JSON summary), though the schema handles this.

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 comprehensive parameter descriptions already provided in the schema (markdown content details, output_path file behavior with return value semantics). Baseline 3 is appropriate as the description focuses on conversion behavior rather than repeating schema details.

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 states a specific verb (Convert) and resources (Markdown to BBCode), and distinguishes from siblings by specifying the target format (BBCode) and supported tags ([b], [i], etc.), clearly positioning it among the many conversion tools available.

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 clear contextual guidance by specifying the target use case ('forum posts on phpBB, vBulletin, and similar platforms'), which helps distinguish it from other converters like convert_to_html or convert_to_docx. Lacks explicit 'when not to use' guidance.

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