minify_json

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

Annotations indicate readOnlyHint=false, which is consistent with a transformation tool. The description adds specific behavioral details: removal of whitespace and unnecessary characters resulting in a compact single-line JSON. This goes beyond what annotations provide, though it does not address error handling or invalid input.

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 extremely concise: two sentences with no wasted words. The first sentence states the action, the second provides a helpful example. Every sentence adds value.

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 description lacks an explicit statement about the return value (e.g., 'Returns the minified JSON string'). While the example hints at the output, a complete description should clarify this, especially since there is no output schema. Also, no mention of error behavior on malformed input.

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% with a clear description for the only parameter ('JSON string to minify'). The tool description does not add significant new information beyond the schema, so baseline score of 3 is 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?

Description clearly states the verb 'minify' and resource 'JSON', explains removal of whitespace and unnecessary characters, and gives an example showing the transformation from formatted to compact single-line. This distinguishes it from related tools like format_json.

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 implies usage when compact JSON is needed, but does not explicitly state when to prefer this over alternatives like format_json. However, the clear purpose and example provide sufficient context for an agent to infer appropriate use.

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