markdown_adf_to_markdown

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

With no annotations, the description carries the full burden. It states 'Supports all ADF elements including panels, tables, media, mentions, and more', which is a useful capability claim. But it does not disclose behavior around invalid ADF, error handling, or output formatting nuances, leaving some behavioral gaps.

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?

The description is three concise sentences, front-loaded with the core purpose in the first sentence. Each subsequent sentence adds context and capability details without redundancy, making it efficient and easy to parse.

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?

While there is no output schema to specify return values, the description names the output as 'Extended Markdown' and claims full ADF element support, providing a good sense of what to expect. It could be slightly more complete by defining 'Extended Markdown' or mentioning limitations, but it is largely sufficient for a single-purpose converter.

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?

The schema provides 100% coverage of the single 'adf' parameter with a clear description of requirements (valid ADF, type 'doc', version 1). The tool's description adds little beyond that, such as the broad element support, but this is more of a capability statement than parameter-specific semantics.

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 a specific verb 'Convert' and resource 'ADF to Extended Markdown', immediately distinguishing it from the sibling reverse tool markdown_markdown_to_adf. It also lists supported element types, reinforcing the converter's scope.

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 description provides context by noting ADF is used in Atlassian products like Jira and Confluence, helping users recognize when they have ADF input. However, it does not explicitly mention when not to use this tool or name the alternative reverse conversion tool, so exclusions are absent.

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