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

No annotations are provided, so the description carries the behavioral burden. It communicates the core transformation and an input precondition ('valid JSON') but does not disclose what happens with invalid input, the output format details, or whether the operation is purely transformative. For a simple stateless formatter this is adequate but not deeply transparent.

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 with no filler. Every word adds value: 'pretty-print' states the action and 'valid JSON text' states the input requirement. It is appropriately minimal for a tool of this simplicity.

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 tool with one string parameter and no output schema, the description is mostly complete: it names the input precondition and the expected transformation. It falls slightly short by not stating invalid-input behavior or confirming the return value, but an agent can reasonably infer the standard formatter behavior.

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 input schema has no property descriptions, giving 0% schema coverage. The description adds some meaning by indicating the 'text' parameter must be valid JSON, but it does not specify encoding, size limits, whitespace handling, or examples. The single parameter named 'text' is fairly self-explanatory, so a mid-range score 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?

The description uses a specific verb and resource: 'Pretty-print valid JSON text.' This clearly differentiates the tool from its JSON-related siblings such as post_json_minify, post_json_validate, and post_json_repair by focusing on formatting rather than validating, repairing, or minifying.

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 states what the tool does but provides no guidance on when to choose it over alternatives. It does not explicitly say to use post_json_minify for compact output or post_json_validate/post_json_repair for invalid JSON. The agent must infer usage context from the tool name and sibling names.

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