json_json_format

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states the action and mentions configurable indentation, but does not address safety, side effects, error conditions, or what happens with invalid input. 'Pretty-print' implies a read-only operation, but this is not explicit.

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 sentence with no wasted words. It is concise and front-loads the key action. However, it could include more useful information without becoming verbose.

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?

Given the tool's simplicity (2 params, output schema exists), the description is adequate but has gaps. It fails to specify that the input must be valid JSON or that an error will occur otherwise. The output is implied but not described. For a simple format tool, it minimally covers the core action.

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 description coverage is 0%, so the description must compensate. It mentions 'configurable indentation' which hints at the indent parameter, but provides no detail about valid values (integer vs null) or that indent specifies spaces. The data parameter is not explained (must be valid JSON string). This adds some value but not enough.

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's action: 'Pretty-print a JSON string with configurable indentation.' The verb 'Pretty-print' is specific and the resource 'JSON string' is well-defined. It distinguishes from sibling tools like json_json_filter, json_json_get, etc., which have different purposes.

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 no guidance on when to use this tool versus alternatives, such as other JSON manipulation tools or formatting tools. There is no mention of when not to use it or any prerequisites. The usage context is entirely implied by the action.

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