json_convert

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

Annotations are absent, so the description carries the burden. It does disclose the bidirectional conversion capability via 'JSON↔XML' etc., but it does not mention error handling, input validation, or the exact return format. This is a moderate amount of behavioral context for a simple transformation tool.

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 a single, compact sentence with the action verb placed first and the list of targets following. It is entirely free of filler and every segment adds meaning.

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 tool with only 3 parameters, all fully described in the schema, and a straightforward output (converted text), the description provides sufficient context. It explains what formats are supported and hints at directionality, though it does not go into details about edge cases or error behavior.

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%, but the description adds significant semantic value by explicitly mapping each 'target' enum value to a concrete format (XML, YAML, GET parameter string) and indicating bidirectionality, which the schema's simple '目标格式' label does not provide.

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: 'JSON 与其他格式互转' (mutually convert JSON with other formats), and specifies the exact target formats (xml, yaml, get_params). This distinguishes it from sibling tools like json_process or text_format by naming concrete conversion targets.

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?

No guidance is provided on when to use this tool versus alternatives such as json_process or data_html_convert. The description only lists available targets, leaving the selection context entirely implicit.

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