json_to_markdown_tool

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

There are no annotations, so the description carries the burden. It does mention that the return value is a 'Dictionary', which is a behavioral trait, but it lacks details about error handling, edge cases (e.g., invalid JSON), or the exact structure of the markdown output.

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 compact, with a one-sentence summary followed by Args and Returns sections. Every element is informative and there is no fluff.

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?

For a simple one-parameter tool with an output schema, the description provides the core purpose and parameter explanation. It lacks usage context and edge-case behavior, but the output schema likely covers return details, making the description sufficient.

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 has zero description coverage, but the tool description explicitly defines 'json_data' as 'JSON string to convert', clarifying the expected input format beyond the bare 'string' type. This adds useful semantic meaning, though it is concise.

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 tool's function with the verb 'converts' and specifies the resource ('JSON data') and output format ('Markdown'). This distinguishes it from sibling tools that focus on fetching or HTML extraction.

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 usage is implied by the stated purpose: when JSON needs to be converted to Markdown, this tool is appropriate. However, there is no explicit guidance about when not to use it or mention of alternatives.

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