convert_to_orgmode

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

Annotations indicate idempotent=true and destructive=false. The description adds valuable behavioral context beyond these flags by detailing specific syntax transformations (headers to *, bold to *text*, code blocks to #+BEGIN_SRC), helping the agent understand the conversion logic and output structure.

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 efficiently convey the tool's purpose and specific transformation rules. Every clause serves a function—first establishing the conversion direction, second detailing syntax mappings—with no redundant or filler text.

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 the 100% schema coverage and presence of annotations, the description provides sufficient context by explaining what gets converted and how. The return behavior is adequately covered in the output_path schema description, making this complete enough for tool selection.

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?

With 100% schema coverage, the structured documentation already comprehensively describes both parameters. The description does not add parameter-specific guidance (e.g., format expectations for the markdown string), warranting the baseline score 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?

The description clearly states the specific action ('Convert') and resources ('Markdown to Emacs Org Mode format'), distinguishing it from 20+ sibling conversion tools by explicitly naming the target format and providing syntax-specific details.

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?

While the description clearly identifies the tool's purpose (converting to Org Mode), it lacks explicit guidance on when to select this specific converter versus siblings like convert_to_asciidoc or convert_to_rst. Usage is implied by the format name but not stated as 'use this when...'.

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