json_to_yaml

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

No annotations are provided, so the description must fully disclose behavior. It only states the conversion, without mentioning error handling for invalid JSON, output format details, or any potential edge cases. The agent is left to infer how the tool behaves beyond the basic transformation.

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, front-loaded sentence that directly states the tool's purpose with no unnecessary words. It is minimal but effective for a simple conversion tool.

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?

The tool is simple with only one parameter and no output schema. The description covers the core purpose, and the output (YAML) is implied. However, it lacks details on invalid input behavior and return value specifics, which are not compensated for by annotations or an output schema, so it is not fully complete.

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 with the parameter 'json' described as 'JSON string'. The description adds no additional semantic information beyond the schema, making the baseline of 3 appropriate.

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 'Convert JSON to YAML' uses a specific verb and clearly states the resource transformation. It is distinct from siblings like yaml_to_json and format_json, making the tool's purpose unambiguous.

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 clearly indicates the tool's function, implying it should be used when JSON needs to be converted to YAML. It does not explicitly state exclusions or alternatives, but the sibling tool 'yaml_to_json' supplies contextual contrast. This is clear context without explicit when-not guidance.

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