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

The description discloses only that the body is discarded. With no annotations present, it fails to state whether the tool returns a boolean, raises an error on invalid JSON, or how strict the validation is. This leaves a significant behavioral gap.

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 short sentences, front-loaded with the purpose and a clear behavioral note about discarding. There is no wasted text.

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 tool with no annotations and no output schema, the description is incomplete: it omits return format, invalid-JSON behavior, and which parameter is the 'body'. The presence of several unrelated parameters adds confusion that the description does not resolve.

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 have schema descriptions, so schema coverage is high and the description adds little per-parameter meaning. The description does not clarify that 'json' is the only relevant parameter and that the other fields are accepted but ignored, which would be valuable given the large schema.

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 specific action, 'Check whether a body is valid JSON', with a clear resource. It is not a tautology and naturally distinguishes this tool from the sibling shape-validation tools because it is the only JSON-specific validator.

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 any alternative, nor are there exclusions or warnings. An agent is not told, for example, to use this before parsing JSON or to prefer another tool for non-JSON validation.

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