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

The description discloses an important behavioral trait: the body is discarded rather than stored or returned. With no annotations present, other behavior such as return value and error handling is left implied, but the disposal note adds useful context.

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 two short sentences with no filler. The main action is front-loaded and the second sentence adds a meaningful side-effect disclosure without wasted words.

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 validation tool, the description plus schema provides a minimally viable picture, but it still leaves gaps: it never maps 'body' to the `json` parameter, does not state what the tool returns, and does not explain the relevance of the other optional fields.

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?

All seven parameters are already described in the input schema, including 'JSON text to validate; discarded after the check', so schema coverage is essentially complete. The description adds no additional parameter-specific meaning beyond referring to 'a body'.

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 states a clear operation: check whether a body is valid JSON, and adds that the body is discarded. It does not explicitly connect 'body' to the `json` parameter or differentiate itself from sibling shape-checking tools, so it misses a fully specific 5.

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?

No guidance is given about when to use this tool versus alternatives such as file-path-ok, browser-url-ok, or the other shape-checking siblings. The description gives no exclusions, prerequisites, or selection conditions.

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