Convert local YAML and JSON files

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

Annotations only give a generic safety profile (readOnly=false, destructive=false, openWorld=false). The description adds substantive behavior: the tool writes and verifies a new file, returns no contents, preserves ordered values, duplicate keys and large number tokens, and may alter formatting, escapes and comments. That fidelity tradeoff and the unsupported-feature list are exactly the kind of context annotations cannot convey.

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?

Four tightly packed sentences with no filler; the core action and format pair lead, followed by fidelity caveats, unsupported cases, and the sort option. Each sentence contributes information the agent needs.

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?

With no output schema, the description correctly states that nothing is returned and that a file is written and verified, and it enumerates unsupported YAML constructs. The notable omission is overwrite behavior for output_path on a mutation tool, which an agent would want to know before invoking.

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 40%, so the description must compensate and largely does: it explains the direction pair implicitly via 'between ... YAML subset and JSON', and says sort_keys is an 'optional natural key sorting on YAML to JSON', adding the applies-only-to-YAML direction constraint the schema lacks. It never mentions the indent parameter (enum 2/4), leaving one gap.

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?

States a specific verb (Convert) and resource (a local UTF-8 file between YAML and JSON), with scope qualifiers like the supported 'website-supported YAML subset'. The YAML↔JSON conversion pair inherently separates it from siblings such as abox_xml_json and abox_json_format, so an agent can identify it without opening the schema.

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?

Usage is implied by the format pair and constrained by explicit unsupported cases (anchors, aliases, custom tags, multiple documents), which helps an agent decide feasibility. However, it never states when to prefer this tool over abox_json_format or abox_xml_json, nor any prerequisites, so routing guidance is only inferable.

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