json_process

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

The description lists the core behaviors (format, compress, etc.) but omits critical details such as error handling for invalid JSON, return format for validate, or side effects on input. With no annotations provided, the description carries the full burden and only partially fulfills it.

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 packs the purpose and action list without wasted words. It is highly concise while remaining informative.

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 has multiple modes and no output schema, so the description should explain return values and error behavior. It covers the action options but leaves out what each action returns and how invalid input is handled, making it incomplete for a tool of this complexity.

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 already covers all three parameters with descriptions, achieving 100% coverage. The tool description mainly restates the action enum values with Chinese labels, adding minimal extra meaning beyond the schema.

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 processes JSON with five explicit operations: format, compress, escape, unescape, and validate. This is a specific verb+resource combination that distinguishes it from sibling tools like json_entity or encode_escape.

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 clear context by enumerating the available actions, implying when the tool should be used. However, it does not explicitly mention alternatives or when not to use it, so it falls short of full guidance.

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