minify_json

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

Description explains the transformation (remove whitespace/unnecessary characters) and output format (compact single-line). Annotations have readOnlyHint: false but tool is a pure function, no side effects mentioned; fine for this scope.

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?

Two sentences, no fluff. Front-loaded with action and example.

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 simple one-parameter tool without output schema, description fully covers what the tool does and its output nature.

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?

Single parameter 'json' with 100% schema coverage (description: 'JSON string to minify'). Description adds example of output format, but baseline 3 applies as schema already defines parameter.

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?

Clearly states verb 'Minify' and resource 'JSON', with concrete example showing transformation from formatted to compact single-line JSON. Distinct from sibling 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?

Usage is implied by the name and description (for reducing JSON size), but no explicit guidance on when to prefer over alternatives like format_json or convert_json_to_csv.

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